I have just repeated the git bisect and confirmed that:
- the problem was introduced in 026cee00
- reverting 026cee00 the problem goes away
That commit includes some modifications in kernel/params.c file. Probably the bug has been introduced by that modifications.
El 21/06/2012, a las 16:49, Geert Uytterhoeven escribió:
> On Thu, Jun 21, 2012 at 4:42 PM, richard -rw- weinberger
> <richard.weinberger@...> wrote:
>> On Thu, Jun 21, 2012 at 4:29 PM, David Fernández <david@...> wrote:
>>> What command should I use to revert that specific commit? I'm not an expert
>>> in git, in fact I just learnt what a 'git bisect' is after your message
>> $ git show 026cee00 > sucker.diff
>> $ patch -p1 -R < sucker.diff
> git revert 026cee00
> git revert -n 026cee00
> if you don't want to commit the revert.
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds