From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>,
Sasha Levin <levinsasha928@gmail.com>,
Asias He <asias.hejun@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 2 (kvmtool)
Date: Thu, 02 Feb 2012 15:28:27 -0800 [thread overview]
Message-ID: <4F2B1C1B.1040700@xenotime.net> (raw)
In-Reply-To: <20120202144516.11b33e667a7cbb8d85d96226@canb.auug.org.au>
On 02/01/2012 07:45 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120201:
On some randconfig i386 builds, I am seeing this:
warning: (KVMTOOL_TEST_ENABLE && AMD_IOMMU) selects PCI_MSI which has unmet direct dependencies (PCI && ARCH_SUPPORTS_MSI)
because ARCH_SUPPORTS_MSI needs both X86_LOCAL_APIC and X86_IO_APIC
but configs don't necessarily have both of them enabled.
Do you want to add more selects here?
(this mess could continue for quite some time with other kconfig symbols)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-02-02 22:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 3:45 linux-next: Tree for Feb 2 Stephen Rothwell
2012-02-02 18:07 ` linux-next: Tree for Feb 2 (media/radio/wl128x) Randy Dunlap
2012-02-02 17:20 ` Manjunatha Halli
2012-02-02 18:40 ` [PATCH] " Randy Dunlap
2012-02-02 18:20 ` Manjunatha Halli
2012-02-05 20:32 ` Randy Dunlap
2012-02-02 18:10 ` linux-next: Tree for Feb 2 (trace/events/sunrpc.h) Randy Dunlap
2012-02-09 2:37 ` Steven Rostedt
2012-02-09 3:14 ` Myklebust, Trond
2012-02-09 3:30 ` Steven Rostedt
2012-02-09 16:14 ` Randy Dunlap
2012-02-02 18:24 ` linux-next: Tree for Feb 2 (fs/jffs2) Randy Dunlap
2012-02-02 23:44 ` Stephen Rothwell
2012-02-03 0:41 ` Brian Norris
2012-02-03 5:37 ` Artem Bityutskiy
2012-02-02 23:28 ` Randy Dunlap [this message]
2012-03-27 10:19 ` linux-next: Tree for Feb 2 (kvmtool) Pekka Enberg
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=4F2B1C1B.1040700@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=asias.hejun@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).