All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"linux-next@vger.kernel.org" <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 10:13:24 -0700	[thread overview]
Message-ID: <4CC074B4.7070708@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010211738530.10348@kaball-desktop>

On 10/21/10 09:53, Stefano Stabellini wrote:
> On Thu, 21 Oct 2010, Konrad Rzeszutek Wilk wrote:
>> On Thu, Oct 21, 2010 at 09:13:16AM -0700, Randy Dunlap wrote:
>>> 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)
>>
>> Thank you,
>>
>> Stefano, this one is yours.
>>
> 
> Yep.
> It was a missing #include in arch/x86/pci/xen.c, I fixed it adding a
> commit to my linux-next branch.

Ack.  Thanks.

> ---
> 
> commit fa4c2e29e4a30dc3e9d3f83944eeea63f78350a5
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date:   Thu Oct 21 17:40:08 2010 +0100
> 
>     xen: add a missing #include to arch/x86/pci/xen.c
>     
>     Add missing #include <asm/io_apic.h> to arch/x86/pci/xen.c.
>     
>     Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> 
> diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c
> index 4f5df3d..4a32df2 100644
> --- a/arch/x86/pci/xen.c
> +++ b/arch/x86/pci/xen.c
> @@ -10,6 +10,7 @@
>  #include <linux/acpi.h>
>  
>  #include <linux/io.h>
> +#include <asm/io_apic.h>
>  #include <asm/pci_x86.h>
>  
>  #include <asm/xen/hypervisor.h>


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2010-10-21 17:14 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 ` linux-next: Tree for October 21 (xen) Randy Dunlap
2010-10-21 16:32   ` Konrad Rzeszutek Wilk
2010-10-21 16:53     ` Stefano Stabellini
2010-10-21 17:13       ` Randy Dunlap [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=4CC074B4.7070708@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.