From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
x86 maintainers <x86@kernel.org>
Subject: Re: linux-next: Tree for Dec 6 (x86, not SMP)
Date: Tue, 06 Dec 2011 12:44:39 -0800 [thread overview]
Message-ID: <4EDE7EB7.7080507@xenotime.net> (raw)
In-Reply-To: <20111206154450.5e2ef2baed27993b23a55802@canb.auug.org.au>
On 12/05/2011 08:44 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20111205:
on x86, when CONFIG_SMP is not enabled:
arch/x86/kernel/cpu/common.c:1149:2: error: 'struct cpuinfo_x86' has no member named 'phys_proc_id'
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-12-06 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 4:44 linux-next: Tree for Dec 6 Stephen Rothwell
2011-12-06 20:44 ` Randy Dunlap [this message]
2011-12-06 19:53 ` linux-next: Tree for Dec 6 (x86, not SMP) Ingo Molnar
2011-12-06 20:58 ` linux-next: Tree for Dec 6 (staging/vme) Randy Dunlap
2011-12-12 17:24 ` Randy Dunlap
2011-12-12 17:04 ` [PATCH] Staging: VME: PIO2: Add GPIOLIB dependancy Martyn Welch
2011-12-12 18:34 ` Randy Dunlap
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=4EDE7EB7.7080507@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).