From: Ingo Molnar <mingo@elte•hu>
To: Vegard Nossum <vegard.nossum@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
linux-next@vger•kernel.org
Subject: Re: linux-next: x86 tree build failure
Date: Fri, 18 Jul 2008 22:10:40 +0200 [thread overview]
Message-ID: <20080718201040.GC27176@elte.hu> (raw)
In-Reply-To: <19f34abd0807170223t7a81dbcfyb860b5e3fc32251c@mail.gmail.com>
* Vegard Nossum <vegard.nossum@gmail•com> wrote:
> On Thu, Jul 17, 2008 at 4:07 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > Hi all,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > arch/x86/kernel/syscall_64.c:27: error: array index in initializer exceeds array bounds
> > arch/x86/kernel/syscall_64.c:27: error: (near initialization for 'sys_call_table')
> > arch/x86/kernel/syscall_64.c:27: warning: excess elements in array initializer
> > arch/x86/kernel/syscall_64.c:27: warning: (near initialization for 'sys_call_table')
> >
> > Reverting commit aa27f95867447916d97c7aa6e5422ff6518630dd ("x86:
> > consolidate header guards") makes it build ok. I found that hard to
> > believe, so I undid the revert and it fails again.
>
> Oh, this is in next already?
>
> The basic problem is that I completely overlooked the fact that some
> headers use the guards of _other_ headers in #if-checks. I think we
> should drop the consolidations completely until I have fixed the
> script to replace the header guard names which are used in other files
> as well. I'm sorry :-/
ok, dropped them from the -next integration rules. Stephen, can you use
the previous version of the x86 branch, or should i reintegrate it now?
Ingo
next prev parent reply other threads:[~2008-07-18 20:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 2:07 linux-next: x86 tree build failure Stephen Rothwell
2008-07-17 9:23 ` Vegard Nossum
2008-07-18 20:10 ` Ingo Molnar [this message]
2008-07-18 20:12 ` Ingo Molnar
2008-07-19 12:11 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-09-11 23:56 Stephen Rothwell
2008-09-12 6:05 ` Joerg Roedel
2008-09-12 7:31 ` Stephen Rothwell
2008-09-12 7:54 ` Joerg Roedel
2008-09-12 8:30 ` Ingo Molnar
2008-09-14 19:52 ` Stephen Rothwell
2008-08-25 10:22 Stephen Rothwell
2008-08-25 10:28 ` Ingo Molnar
2008-06-17 3:46 Stephen Rothwell
2008-06-17 5:58 ` Ingo Molnar
2008-06-17 6:08 ` Ingo Molnar
2008-06-17 6:45 ` Ingo Molnar
2008-06-18 5:04 ` Stephen Rothwell
2008-06-18 6:39 ` Ingo Molnar
2008-06-25 3:17 ` Stephen Rothwell
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=20080718201040.GC27176@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=vegard.nossum@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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