linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: xen-devel@lists.xenproject.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] linux-next: Tree for May 2 (xen: events_base.c)
Date: Tue, 2 May 2017 11:58:23 -0400	[thread overview]
Message-ID: <67b83f68-eaad-20c8-c2ef-44c43d97e0ed@oracle.com> (raw)
In-Reply-To: <cf1e1487-dc87-cccc-5574-3706da37a7e2@infradead.org>

On 05/02/2017 11:34 AM, Randy Dunlap wrote:
> On 05/01/17 23:47, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v4.13 destined material in your linux-next
>> included branches until after v4.12-rc1 has been released.
>>
>> Changes since 20170501:
>>
> on x86_64:
>
> drivers/built-in.o: In function `set_affinity_irq':
> events_base.c:(.text+0x1632c4): undefined reference to `xen_have_vector_callback'
> arch/x86/pci/built-in.o: In function `pci_xen_hvm_init':
> (.init.text+0x59f): undefined reference to `xen_have_vector_callback'
>
>


Can you send me (or to the list) your config file?


Thanks.
-boris

  reply	other threads:[~2017-05-02 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  6:47 linux-next: Tree for May 2 Stephen Rothwell
2017-05-02 15:34 ` linux-next: Tree for May 2 (xen: events_base.c) Randy Dunlap
2017-05-02 15:58   ` Boris Ostrovsky [this message]
2017-05-02 16:03     ` [Xen-devel] " 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=67b83f68-eaad-20c8-c2ef-44c43d97e0ed@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xen-devel@lists.xenproject.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).