From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: tip-core tree build wanings
Date: Sun, 14 Sep 2008 17:05:23 +0200 [thread overview]
Message-ID: <20080914150523.GJ12522@elte.hu> (raw)
In-Reply-To: <20080912150753.1ce5002c.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next build (powerpc_ppc64_defconfig) produced lots of
> warnings like this:
>
> In file included from arch/powerpc/platforms/powermac/smp.c:24:
> include/linux/kernel.h:498:1: warning: "BUILD_BUG_ON" redefined
> In file included from include/linux/linkage.h:4,
> from include/linux/kernel.h:11,
> from arch/powerpc/platforms/powermac/smp.c:24:
> include/linux/compiler.h:209:1: warning: this is the location of the previous definition
>
> Introduced by commit 3cff9a338bd3ace9cfb501e08aeb69913b47c53d ("manual
> merge of core/debug") which recreated the definition of the BUILD_BUG_ON
> macro in kernel.h.
>
> I applied the following patch.
ah, both of these patches were reverted in tip/master 4 days ago:
49937ca: Revert "debug: fix BUILD_BUG_ON() for non-constant expressions"
c3d4a3c: Revert "debug, x86: move BUILD_BUG_ON() and __FUNCTION__"
i've cherry-picked them over into tip/auto-core-next. Thanks,
Ingo
next prev parent reply other threads:[~2008-09-14 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 5:07 linux-next: tip-core tree build wanings Stephen Rothwell
2008-09-14 15:05 ` Ingo Molnar [this message]
2008-09-14 18:10 ` 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=20080914150523.GJ12522@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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