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>,
Linus <torvalds@linux-foundation.org>,
Michal Marek <mmarek@suse.cz>, x86 maintainers <x86@kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: linux-next: Tree for Nov 3 (KVMTOOL_TEST_ENABLE)
Date: Fri, 04 Nov 2011 09:59:33 -0700 [thread overview]
Message-ID: <4EB419F5.6070308@xenotime.net> (raw)
In-Reply-To: <4EB33525.808@xenotime.net>
On 11/03/2011 05:43 PM, Randy Dunlap wrote:
> On 11/02/2011 11:20 PM, Stephen Rothwell wrote:
>> Hi all,
>
>
> When KVMTOOL_TEST_ENABLE is enabled but CONFIG_BLOCK is not enabled, there are
> MANY build errors. This one (case) is probably fixed by adding "select BLOCK", but it's
> all rather ugly.
kconfig even tells us:
warning: (KVMTOOL_TEST_ENABLE) selects KGDB which has unmet direct dependencies (HAVE_ARCH_KGDB && DEBUG_KERNEL && EXPERIMENTAL)
warning: (KVMTOOL_TEST_ENABLE) selects BLK_DEV which has unmet direct dependencies (BLOCK)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-11-04 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 6:20 linux-next: Tree for Nov 3 Stephen Rothwell
2011-11-03 7:29 ` Sedat Dilek
2011-11-03 11:41 ` Stephen Rothwell
2011-11-03 21:47 ` linux-next: Tree for Nov 3 (staging/et131x) Randy Dunlap
2011-11-04 10:27 ` Mark Einon
2011-11-04 15:53 ` Randy Dunlap
2011-11-04 17:58 ` [PATCH] linux-next: et131x: Fix build error when CONFIG_PM_SLEEP not enabled Mark Einon
2011-11-04 18:19 ` Randy Dunlap
2011-11-04 0:43 ` linux-next: Tree for Nov 3 (KVMTOOL_TEST_ENABLE) Randy Dunlap
2011-11-04 16:59 ` Randy Dunlap [this message]
2011-11-04 20:03 ` Pekka Enberg
2011-11-07 17:34 ` 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=4EB419F5.6070308@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=penberg@cs.helsinki.fi \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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.