From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: linux-next: Tree for Nov 1 (xen_swiotllb) Date: Fri, 01 Nov 2013 11:16:26 -0700 Message-ID: <5273EFFA.1030400@infradead.org> References: <20131101191138.442028fb1f243c7f9c7f0844@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from merlin.infradead.org ([205.233.59.134]:56746 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754032Ab3KASQ3 (ORCPT ); Fri, 1 Nov 2013 14:16:29 -0400 In-Reply-To: <20131101191138.442028fb1f243c7f9c7f0844@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell , linux-next@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Konrad Rzeszutek Wilk , xen-devel@lists.xenproject.org On 11/01/13 01:11, Stephen Rothwell wrote: > Hi all, > > Changes since 20131031: > > The squashfs tree gained a build failure so I used the version from > next-20131031. > > The block tree gained conflicts against the f2fs, aio-direct and Linus' > trees and a build failure and generated several warnings so I used the > version from next-20131031. > > The dt-rh tree gained a conflict against the powerpc tree. > > The kvm-ppc tree gained a conflict against the powerpc tree. > > The leds tree gained a conflict against the powerpc tree. > > The tty tree lost its build failure. on x86_64, when CONFIG_PCI is not enabled: arch/x86/built-in.o: In function `pci_xen_swiotlb_init_late': (.text+0x102cc): undefined reference to `pci_request_acs' arch/x86/built-in.o: In function `pci_xen_swiotlb_init': (.init.text+0x3f6c): undefined reference to `pci_request_acs' -- ~Randy