[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160308092152.GE12413@gmail.com>
Date: Tue, 8 Mar 2016 10:21:52 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: kbuild test robot <fengguang.wu@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
"kbuild-all@...org" <kbuild-all@...org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: kernel/irq/irqdesc.c:206:2: error: array index in initializer
exceeds array bounds
* Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> On Tue, Mar 8, 2016 at 9:38 AM, kbuild test robot
> <fengguang.wu@...el.com> wrote:
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: e2857b8f11a289ed2b61d18d0665e05c1053c446
> > 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
> >
> > 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
> > ^
> > include/linux/irqnr.h:15:19: note: in expansion of macro 'NR_IRQS'
> > #define nr_irqs NR_IRQS
> > ^
> > kernel/irq/irqdesc.c:36:5: note: in expansion of macro 'nr_irqs'
> > int nr_irqs = NR_IRQS;
> > ^
> >>> kernel/irq/irqdesc.c:206:2: error: array index in initializer exceeds array bounds
> > [0 ... NR_IRQS-1] = {
> > ^
>
> Same comment as before: thou shall not compile kernels for m68k without
> selecting any platform support.
That should be enforced at the Kconfig level.
Thanks,
Ingo
Powered by blists - more mailing lists