From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [Xen-devel] linux-next: Tree for May 2 (xen: events_base.c) Date: Tue, 2 May 2017 11:58:23 -0400 Message-ID: <67b83f68-eaad-20c8-c2ef-44c43d97e0ed@oracle.com> References: <20170502164733.59f7d208@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from aserp1040.oracle.com ([141.146.126.69]:35669 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750961AbdEBP7L (ORCPT ); Tue, 2 May 2017 11:59:11 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Randy Dunlap , Stephen Rothwell , Linux-Next Mailing List Cc: xen-devel@lists.xenproject.org, Linux Kernel Mailing List 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