[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5273EFFA.1030400@infradead.org>
Date: Fri, 01 Nov 2013 11:16:26 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org
CC: linux-kernel@...r.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
xen-devel@...ts.xenproject.org
Subject: Re: linux-next: Tree for Nov 1 (xen_swiotllb)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists