On Friday 27 May 2005 05:31, Paul Mundt wrote:
> On Fri, May 27, 2005 at 03:06:09AM +0200, Blaisorblade wrote:
> > On Friday 27 May 2005 02:38, [EMAIL PROTECTED] wrote:
> > Ok, a grep shows that possible culprits (i.e. giving success to
> > grep GENERIC_HARDIRQS arch/*/Kconfig, and using 0x400
On Friday 27 May 2005 15:33, David Howells wrote:
> Blaisorblade <[EMAIL PROTECTED]> wrote:
> > Ok, a grep shows that possible culprits (i.e. giving success to
> > grep GENERIC_HARDIRQS arch/*/Kconfig, and using 0x400 as
> > PREEMPT_ACTIVE, as given by grep PREEMPT_ACTIVE
> > include/asm-*/thre
Blaisorblade <[EMAIL PROTECTED]> wrote:
> Ok, a grep shows that possible culprits (i.e. giving success to
> grep GENERIC_HARDIRQS arch/*/Kconfig, and using 0x400 as PREEMPT_ACTIVE,
> as given by grep PREEMPT_ACTIVE include/asm-*/thread_info.h) are (at a first
> glance): frv, sh, sh64.
For F
On Fri, May 27, 2005 at 03:06:09AM +0200, Blaisorblade wrote:
> On Friday 27 May 2005 02:38, [EMAIL PROTECTED] wrote:
> > After porting this fixlet to UML:
> >
> > http://linux.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]
> >
> > , I've also added a warning which should refuse compilation with insan
On Friday 27 May 2005 02:38, [EMAIL PROTECTED] wrote:
> After porting this fixlet to UML:
>
> http://linux.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]
>
> , I've also added a warning which should refuse compilation with insane
> values for PREEMPT_ACTIVE... maybe we should simply move PREEMPT_ACTIV
5 matches
Mail list logo