mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Mike Waychison <mikew@google.com>
Cc: gregkh@linuxfoundation.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware/google: drop 'select EFI' to avoid recursive dependency
Date: Thu, 23 Jan 2014 13:36:55 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1401231334540.7313@chino.kir.corp.google.com> (raw)
In-Reply-To: <1390473588-23367-1-git-send-email-ard.biesheuvel@linaro.org>

On Thu, 23 Jan 2014, Ard Biesheuvel wrote:

> The GOOGLE_SMI Kconfig symbol depends on DMI and selects EFI. This
> causes problems on other archs when introducing DMI support that
> depends on EFI, as it results in a recursive dependency:
> 
> arch/arm/Kconfig:1845:error: recursive dependency detected!
> arch/arm/Kconfig:1845:	symbol DMI depends on EFI
> 
> Fix by changing the 'select EFI' to a 'depends on EFI'.
> 
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
>  drivers/firmware/google/Kconfig | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/firmware/google/Kconfig b/drivers/firmware/google/Kconfig
> index 2f21b0bfe653..29c8cdda82a1 100644
> --- a/drivers/firmware/google/Kconfig
> +++ b/drivers/firmware/google/Kconfig
> @@ -12,8 +12,7 @@ menu "Google Firmware Drivers"
>  
>  config GOOGLE_SMI
>  	tristate "SMI interface for Google platforms"
> -	depends on ACPI && DMI
> -	select EFI
> +	depends on ACPI && DMI && EFI
>  	select EFI_VARS
>  	help
>  	  Say Y here if you want to enable SMI callbacks for Google

Adding Mike Waychison <mikew@google.com> to the cc since this is his code, 
but it looks good to me.

$ ./scripts/get_maintainer.pl -f drivers/firmware/google/Kconfig
linux-kernel@vger.kernel.org (open list)

I wonder why he's not listed as a recipient for patches from 
get_maintainer.pl since it's clearly obvious he wrote the entire file.

  reply	other threads:[~2014-01-23 21:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 10:39 Ard Biesheuvel
2014-01-23 21:36 ` David Rientjes [this message]
2014-01-23 21:40   ` Mike Waychison
2014-01-23 21:48     ` Ard Biesheuvel
2014-01-23 21:49   ` Andrew Morton
2014-01-23 22:45     ` David Rientjes
2014-01-24  0:02       ` Joe Perches
2014-01-24 10:27         ` David Rientjes
2014-01-24 22:56           ` Joe Perches
2014-01-24 23:17             ` David Rientjes

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=alpine.DEB.2.02.1401231334540.7313@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    /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

all inboxes | Powered by JetHome®