From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the final tree
Date: Mon, 02 Aug 2010 18:03:50 +1000 [thread overview]
Message-ID: <1280736230.1902.56.camel@pasglop> (raw)
In-Reply-To: <20100802141035.f84f9132.sfr@canb.auug.org.au>
On Mon, 2010-08-02 at 14:10 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig with CONFIG_DEBUG_SECTION_MISMATCH=y) produced these warnings:
.../...
> Introduced by the memblock series in the tip tree.
Ok, so those are my fault but none are deadly. I'll do a fixup patch on
top of this.
Cheers,
Ben.
next prev parent reply other threads:[~2010-08-02 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 4:10 linux-next: build warnings after merge of the final tree Stephen Rothwell
2010-08-02 8:03 ` Benjamin Herrenschmidt [this message]
2010-08-02 8:51 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2011-12-14 7:15 Stephen Rothwell
2011-12-14 7:15 ` Stephen Rothwell
2011-12-14 7:15 ` Stephen Rothwell
2011-12-14 16:32 ` Steven Rostedt
2011-12-14 16:32 ` Steven Rostedt
2011-12-14 16:47 ` H. Peter Anvin
2011-12-14 16:47 ` H. Peter Anvin
2011-12-22 5:33 ` Stephen Rothwell
2011-12-22 5:33 ` Stephen Rothwell
2012-01-04 8:06 ` Stephen Rothwell
2012-01-04 8:06 ` Stephen Rothwell
2012-01-04 9:23 ` hpanvin@gmail.com
2012-01-04 9:23 ` hpanvin@gmail.com
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=1280736230.1902.56.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.