Re: Bisecting tip/auto-x86-next?

[Ingo Molnar]

* Kevin Winchester <kjwinchester@xxxxxxxxx> wrote:

>
> Hi,
>
> I am trying to track down a problem I reported here:
>
> http://lkml.org/lkml/2008/6/11/431
>
> None or you were cc'd on the original report because I had no idea of  
> the source of the issue.  However, I have now narrowed down the problem  
> to the auto-x86-next tree.  Thus I did something like:
>
> $ git bisect start
> $ git bisect good linus/master
> $ git bisect bad tip/auto-x86-next
>
> which resulted in only about 170 or so revisions to test (sounds better  
> than the 3000 or so that -next wanted me to bisect through).  However,  
> when I tried to compile the bisect-chosen commit, I get:
>
> ------------------
>
> In file included from include/asm/thread_info.h:5,
>                  from include/linux/thread_info.h:47,
>                  from include/linux/preempt.h:9,
>                  from include/linux/spinlock.h:49,
>                  from include/linux/seqlock.h:29,
>                  from include/linux/time.h:8,
>                  from include/linux/stat.h:60,
>                  from include/linux/module.h:10,
>                  from crypto/sha1_generic.c:20:
> include/asm/thread_info_64.h: In function âset_restore_sigmaskâ:
> include/asm/thread_info_64.h:189: warning: passing argument 2 of  
> âset_bitâ from incompatible pointer type

hm, could you send me the config that triggered this?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/