From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 26 (xen)
Date: Mon, 26 Jul 2010 17:38:40 -0700 [thread overview]
Message-ID: <4C4E2A90.3040902@goop.org> (raw)
In-Reply-To: <20100726091651.f4ed28b8.randy.dunlap@oracle.com>
On 07/26/2010 09:16 AM, Randy Dunlap wrote:
> On Mon, 26 Jul 2010 15:48:09 +1000 Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20100723:
>>
>> Undropped tree: xen
>>
>> The xen tree lost its build problems but gained a couple more for which I
>> reverted a commit and a subtreee.
>
> when CONFIG_SMP is not enabled:
>
> arch/x86/xen/enlighten.c:112: error: 'setup_max_cpus' undeclared (first use in this function)
Thanks, I've fixed it up.
J
prev parent reply other threads:[~2010-07-27 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 5:48 linux-next: Tree for July 26 Stephen Rothwell
2010-07-26 8:53 ` Michal Simek
2010-07-26 9:19 ` Stephen Rothwell
2010-07-26 16:16 ` linux-next: Tree for July 26 (xen) Randy Dunlap
2010-07-27 0:38 ` Jeremy Fitzhardinge [this message]
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=4C4E2A90.3040902@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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.