Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752033AbbBSCFI (ORCPT ); Wed, 18 Feb 2015 21:05:08 -0500 Received: from ozlabs.org ([103.22.144.67]:40444 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751501AbbBSCFG (ORCPT ); Wed, 18 Feb 2015 21:05:06 -0500 From: Rusty Russell To: Randy Dunlap , Stephen Rothwell , linux-next@vger.kernel.org Cc: linux-kernel@vger.kernel.org, X86 ML , lguest@lists.ozlabs.org Subject: Re: linux-next: Tree for Feb 18 (x86) In-Reply-To: <54E51603.8040601@infradead.org> References: <20150218142237.2cc68be5@canb.auug.org.au> <54E4DE1C.1020503@infradead.org> <54E51603.8040601@infradead.org> User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Thu, 19 Feb 2015 12:31:05 +1030 Message-ID: <87mw4aslr2.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1273 Lines: 44 Randy Dunlap 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 Signed-off-by: Rusty Russell 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/