mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	"kbuild-all@01.org" <kbuild-all@01.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: kernel/irq/irqdesc.c:206:2: error: array index in initializer exceeds array bounds
Date: Sun, 28 Feb 2016 11:33:32 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1602281132020.3638@nanos> (raw)
In-Reply-To: <CAMuHMdUSQ9Y1=1D_LTKdt8rzMVveLQ50P7QQhjh+=hVZsD=CLA@mail.gmail.com>

On Sun, 28 Feb 2016, Geert Uytterhoeven wrote:
> On Sun, Feb 28, 2016 at 10:32 AM, Thomas Gleixner <tglx@linutronix.de> 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?

# make alldefconfig

That's one of the targets for 68k. And yes, it has MMU=y

> 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.

Yeah. NR_IRQS=1 is lame.

Thanks,

	tglx

  reply	other threads:[~2016-02-28 10:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2016-02-28 10:41       ` Geert Uytterhoeven
2016-03-08  8:38 kbuild test robot
2016-03-08  8:44 ` Geert Uytterhoeven
2016-03-08  9:21   ` Ingo Molnar
2016-03-08 10:09     ` Geert Uytterhoeven
2016-03-08  9:08 ` Thomas Gleixner
2016-03-13 20:29 kbuild test robot
2016-03-14  7:53 ` Thomas Gleixner

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=alpine.DEB.2.11.1602281132020.3638@nanos \
    --to=tglx@linutronix.de \
    --cc=fengguang.wu@intel.com \
    --cc=geert@linux-m68k.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    /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®