From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
xen-devel@lists•xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for October 21 (xen)
Date: Thu, 21 Oct 2010 09:13:16 -0700 [thread overview]
Message-ID: <20101021091316.0587c1a8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101021151529.392fecea.sfr@canb.auug.org.au>
On Thu, 21 Oct 2010 15:15:29 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Reminder: do not add 2.6.38 destined stuff to linux-next until after
> 2.6.37-rc1 is released.
>
> Changes since 20101020:
When CONFIG_SMP is not enabled:
arch/x86/pci/xen.c:401: error: 'nr_ioapics' undeclared (first use in this function)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-21 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 4:15 linux-next: Tree for October 21 Stephen Rothwell
2010-10-21 16:13 ` Randy Dunlap [this message]
2010-10-21 16:32 ` linux-next: Tree for October 21 (xen) Konrad Rzeszutek Wilk
2010-10-21 16:53 ` Stefano Stabellini
2010-10-21 17:13 ` 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=20101021091316.0587c1a8.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=xen-devel@lists$(echo .)xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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