From: Ingo Molnar <mingo@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: kernel/irq/irqdesc.c:206:2: error: array index in initializer exceeds array bounds
Date: Tue, 8 Mar 2016 10:21:52 +0100 [thread overview]
Message-ID: <20160308092152.GE12413@gmail.com> (raw)
In-Reply-To: <CAMuHMdX4C7UAw9KuAqrCaBUTHCZ=F6MeVr4NfLtSPu0GTCoYEA@mail.gmail.com>
* Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Tue, Mar 8, 2016 at 9:38 AM, kbuild test robot
> <fengguang.wu@intel.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
next prev parent reply other threads:[~2016-03-08 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 8:38 kbuild test robot
2016-03-08 8:44 ` Geert Uytterhoeven
2016-03-08 9:21 ` Ingo Molnar [this message]
2016-03-08 10:09 ` Geert Uytterhoeven
2016-03-08 9:08 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2016-03-13 20:29 kbuild test robot
2016-03-14 7:53 ` Thomas Gleixner
2016-02-27 23:59 kbuild test robot
2016-02-28 9:32 ` Thomas Gleixner
2016-02-28 9:52 ` Geert Uytterhoeven
2016-02-28 10:33 ` Thomas Gleixner
2016-02-28 10:41 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160308092152.GE12413@gmail.com \
--to=mingo@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®