All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Randy Dunlap <rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: lguest-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	X86 ML <x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: linux-next: Tree for Feb 18 (x86)
Date: Thu, 19 Feb 2015 12:31:05 +1030	[thread overview]
Message-ID: <87mw4aslr2.fsf@rustcorp.com.au> (raw)
In-Reply-To: <54E51603.8040601-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

Randy Dunlap <rdunlap@infradead.org> writes:
> On 02/18/15 10:46, Randy Dunlap wrote:
>> On 02/17/15 19:22, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do not add any material destined for v3.21 to your linux-next
>>> included trees until after v3.20-rc1 has been released.
>>>
>>> Changes since 20150217:
>>>
>> 
>> 
>> on i386, when CONFIG_PCI is not enabled:
>
> This is all lguest-related.  Looks like LGUEST_GUEST should also
> depend on PCI (in arch/x86/lguest/Kconfig).

I've committed this to my fixes branch.

Thanks,
Rusty.

lguest: now depends on PCI

Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

diff --git a/arch/x86/lguest/Kconfig b/arch/x86/lguest/Kconfig
index 4a0890f815c4..21e89807244c 100644
--- a/arch/x86/lguest/Kconfig
+++ b/arch/x86/lguest/Kconfig
@@ -1,6 +1,6 @@
 config LGUEST_GUEST
 	bool "Lguest guest support"
-	depends on X86_32 && PARAVIRT
+	depends on X86_32 && PARAVIRT && PCI
 	select TTY
 	select VIRTUALIZATION
 	select VIRTIO
_______________________________________________
Lguest mailing list
Lguest@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/lguest

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, X86 ML <x86@kernel.org>,
	lguest@lists.ozlabs.org
Subject: Re: linux-next: Tree for Feb 18 (x86)
Date: Thu, 19 Feb 2015 12:31:05 +1030	[thread overview]
Message-ID: <87mw4aslr2.fsf@rustcorp.com.au> (raw)
In-Reply-To: <54E51603.8040601@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:
> On 02/18/15 10:46, Randy Dunlap wrote:
>> On 02/17/15 19:22, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do not add any material destined for v3.21 to your linux-next
>>> included trees until after v3.20-rc1 has been released.
>>>
>>> Changes since 20150217:
>>>
>> 
>> 
>> on i386, when CONFIG_PCI is not enabled:
>
> This is all lguest-related.  Looks like LGUEST_GUEST should also
> depend on PCI (in arch/x86/lguest/Kconfig).

I've committed this to my fixes branch.

Thanks,
Rusty.

lguest: now depends on PCI

Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

diff --git a/arch/x86/lguest/Kconfig b/arch/x86/lguest/Kconfig
index 4a0890f815c4..21e89807244c 100644
--- a/arch/x86/lguest/Kconfig
+++ b/arch/x86/lguest/Kconfig
@@ -1,6 +1,6 @@
 config LGUEST_GUEST
 	bool "Lguest guest support"
-	depends on X86_32 && PARAVIRT
+	depends on X86_32 && PARAVIRT && PCI
 	select TTY
 	select VIRTUALIZATION
 	select VIRTIO

  parent reply	other threads:[~2015-02-19  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  3:22 linux-next: Tree for Feb 18 Stephen Rothwell
2015-02-18 18:46 ` linux-next: Tree for Feb 18 (x86) Randy Dunlap
2015-02-18 22:45   ` Randy Dunlap
     [not found]     ` <54E51603.8040601-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-02-19  2:01       ` Rusty Russell [this message]
2015-02-19  2:01         ` Rusty Russell

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=87mw4aslr2.fsf@rustcorp.com.au \
    --to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
    --cc=lguest-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.