On Sun, Feb 28, 2016 at 10:32 AM, Thomas Gleixner <[email protected]> wrote:
> On Sun, 28 Feb 2016, kbuild test robot wrote:
>> FYI, the error/warning still remains.
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
>> master
>> head:   691429e13dfaf5b0994b07cc166db41bd608ee3d
>> commit: 3795de236d67a05994a1a12759db9d4dd9ffc42c genirq: Distangle 
>> kernel/irq/handle.c
>> date:   5 years ago
>> config: m68k-alldefconfig (attached as .config)
>> reproduce:
>>         wget 
>> https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
>>  -O ~/bin/make.cross
>>         chmod +x ~/bin/make.cross
>>         git checkout 3795de236d67a05994a1a12759db9d4dd9ffc42c
>>         # save the attached .config to linux build tree
>>         make.cross ARCH=m68k
>
> Again. This commit is just moving code into seperate files without changing
> the code. So it's not a new wreckage.
>
>> All errors (new ones prefixed by >>):
>>
>>    In file included from include/linux/irqnr.h:10:0,
>>                     from include/linux/irq.h:22,
>>                     from kernel/irq/irqdesc.c:10:
>>    arch/m68k/include/asm/irq.h:25:17: error: expected identifier or '(' 
>> before numeric constant
>>     #define NR_IRQS 0
>>                     ^
>
> NR_IRQS = 0 and CONFIG_SPARSE_IRQ=n is bogus. That alldefconfig of m68k is
> broken. Cc'ed m68 folks

No idea where this "alldefconfig" is coming from (it contains "2.6.36-rc5").
Is this an MMU=y allnoconfig?
It doesn't enable any platforms, which is not supported, and thus it isn't
known how many interrupts are needed.

BTW, I have a local fix to change NR_IRQS to 1 in that case, but that's
far from sufficient to build an MMU=y allnoconfig kernel.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

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

Reply via email to