From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Jeremy Fitzhardinge <jeremy@xensource.com>
Cc: 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 09:16:51 -0700 [thread overview]
Message-ID: <20100726091651.f4ed28b8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100726154809.7f42c137.sfr@canb.auug.org.au>
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)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-07-26 16:17 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 ` Randy Dunlap [this message]
2010-07-27 0:38 ` linux-next: Tree for July 26 (xen) Jeremy Fitzhardinge
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=20100726091651.f4ed28b8.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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).