From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Feng Tang <feng.tang@intel.com>
Subject: Re: linux-next: Tree for October 13
Date: Wed, 13 Oct 2010 17:41:08 -0700 [thread overview]
Message-ID: <4CB651A4.60205@zytor.com> (raw)
In-Reply-To: <20101013173826.f4b911b4.akpm@linux-foundation.org>
On 10/13/2010 05:38 PM, Andrew Morton wrote:
> On Wed, 13 Oct 2010 15:45:22 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>> I have created today's linux-next tree at
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
> In an i386 allmodconfig build, compilation of
> arch/x86/kernel/early_printk_mrst.c is emitting a call to
> __this_fixmap_does_not_exist().
Will look at it. Do you happen to have toolchain versions?
-hpa
next prev parent reply other threads:[~2010-10-14 0:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 4:45 linux-next: Tree for October 13 Stephen Rothwell
2010-10-13 16:38 ` linux-next: Tree for October 13 (net/3c59x) Randy Dunlap
2010-10-13 16:54 ` David Miller
2010-10-13 16:41 ` linux-next: Tree for October 13 (staging/iio) Randy Dunlap
2010-10-13 19:07 ` Hennerich, Michael
2010-10-14 10:21 ` Jonathan Cameron
2010-10-13 19:57 ` [PATCH -next] gpu/drm: fix build errors and kconfig dependency warnings Randy Dunlap
2010-10-14 0:38 ` linux-next: Tree for October 13 Andrew Morton
2010-10-14 0:41 ` H. Peter Anvin [this message]
2010-10-14 0:47 ` Andrew Morton
2010-10-14 2:55 ` Tony Breeds
2010-10-14 9:41 ` Feng Tang
-- strict thread matches above, loose matches on Subject: below --
2009-10-13 5:23 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=4CB651A4.60205@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).