From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: [PATCH -next] firmware: fix GOOGLE_SMI kconfig dependency warning Date: Sun, 22 May 2011 17:38:02 -0700 Message-ID: <20110522173802.c0766c64.randy.dunlap@oracle.com> References: <20110520165507.cba539d5.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110520165507.cba539d5.sfr@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell , Mike Waychison Cc: linux-next@vger.kernel.org, LKML , gregkh List-Id: linux-next.vger.kernel.org From: Randy Dunlap Is it meaningful/useful to enable EFI_VARS but not EFI? That's what GOOGLE_SMI does. Make it enable EFI also. Fixes this kconfig dependency warning: warning: (GOOGLE_SMI) selects EFI_VARS which has unmet direct dependencies (EFI) Signed-off-by: Randy Dunlap Cc: Mike Waychison --- drivers/firmware/google/Kconfig | 1 + 1 file changed, 1 insertion(+) --- linux-next-20110520.orig/drivers/firmware/google/Kconfig +++ linux-next-20110520/drivers/firmware/google/Kconfig @@ -13,6 +13,7 @@ menu "Google Firmware Drivers" config GOOGLE_SMI tristate "SMI interface for Google platforms" depends on ACPI && DMI + select EFI select EFI_VARS help Say Y here if you want to enable SMI callbacks for Google