From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xenproject.org
Subject: Re: linux-next: Tree for Nov 1 (xen_swiotllb)
Date: Fri, 01 Nov 2013 11:16:26 -0700 [thread overview]
Message-ID: <5273EFFA.1030400@infradead.org> (raw)
In-Reply-To: <20131101191138.442028fb1f243c7f9c7f0844@canb.auug.org.au>
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
next prev parent reply other threads:[~2013-11-01 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 8:11 linux-next: Tree for Nov 1 Stephen Rothwell
2013-11-01 8:11 ` Stephen Rothwell
2013-11-01 18:16 ` Randy Dunlap [this message]
2013-11-01 19:43 ` linux-next: Tree for Nov 1 (xen_swiotllb) Konrad Rzeszutek Wilk
2013-11-01 19:43 ` Konrad Rzeszutek Wilk
2013-11-04 18:20 ` Stefano Stabellini
2013-11-04 18:20 ` Stefano Stabellini
2013-11-04 18:25 ` Konrad Rzeszutek Wilk
2013-11-04 18:25 ` Konrad Rzeszutek Wilk
2013-11-04 18:20 ` Stefano Stabellini
2013-11-01 18:16 ` Randy Dunlap
2013-11-01 18:28 ` linux-next: Tree for Nov 1 (dm-delay, dm-flakey) 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=5273EFFA.1030400@infradead.org \
--to=rdunlap@infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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.