kexec 2.0.2 MIPS

[ANDY KENNEDY]

> My bad, yes the idea is to check between 2.0.1 and 2.0.2.
> I will explain git bisect further down. However, it looking at the
> logs
> it strikes me that there was only one significant MIPS change
> between
> 2.0.1 and 2.0.2. So that seems like a likely culprit.
> 
> Could you try the following?
> 
> $ git clone git://github.com/horms/kexec-tools.git
> $ cd kexec-tools
> $ git checkout 6adc05c6e3fdbc8b9f5d915af78ca05d0a09cb17^

Works.

> 
> Build and see if it works. If so could you then try?
> 
> $ git checkout 6adc05c6e3fdbc8b9f5d915af78ca05d0a09cb17

Works.

> 
> Build and see if it works. If it does not then
> revision 6adc05c6e3fdbc8b9f5d915af78ca05d0a09cb17 starts to smell
> a lot like the cause of the problem you have observed.
> 
> 
> Git Bisect
> ----------
> 
> A git bisection works by doing a binary search over a set of
> commits
> in order to (hopefully) isolate which commit introduces a
> regression.
> 
> To this, the git commands are something along these lines:
> 
> $ git clone git://github.com/horms/kexec-tools.git
> $ cd kexec-tools
> $ git checkout v2.0.1

root at akennedy_lin:~/src/kexec/kexec-tools# git checkout v2.0.1
error: pathspec 'v2.0.1' did not match any file(s) known to git.
(yes, I run as root.  Have since 1994, so, please no holy wars.)

> 
> Build and confirm that it does work
> 
> $ git checkout v2.0.2
> 
> Build and confirm that it does not work.
> 
> Now we actually start the bisect
> 
> $ git bisect start
> $ git bisect bad v2.0.2
> $ git bisect good v2.0.1
> 
> Git should now select a revision between v2.0.1 and v2.0.2
> Test it and see if it works or not. If it does run
> 
> $ git bisect good
> If not run
> 
> $ git bisect bad
> 
> Git will now select another revision for you to test...

I have some time right now to test, so, when you can get
back to me I'll be able to continue.