All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Olof Johansson <olof@lixom.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Doug Anderson <dianders@chromium.org>,
	Gwendal Grignou <gwendal@chromium.org>,
	Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: Make CROS_EC_PROTO a user selectable option
Date: Tue, 18 Aug 2015 14:40:12 +0200	[thread overview]
Message-ID: <1525696.gQFOjPpKHL@amdc1976> (raw)
In-Reply-To: <1439882106-23406-1-git-send-email-javier@osg.samsung.com>


Hi,

On Tuesday, August 18, 2015 09:15:06 AM Javier Martinez Canillas wrote:
> The boolean CROS_EC_PROTO symbol is selected by MFD_CROS_EC but that can
> cause Kconfig circular dependencies so is better to change the select to

Could you please give a reference to the problem or error message
that you're getting (I was not following the previous discussion).

> a depends on. But in order to be able to change that, the CROS_EC_PROTO
> symbol has to be one that can be selected by the user.

Looking at the code behind the config option it seems that it is just
a helper library and should not be made user-visible.  Why can't
the issue be fixed the other way (make other config options select
CROS_EC_PROTO consistently)?

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> ---
>  drivers/platform/chrome/Kconfig | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig
> index 3271cd1abe7c..a73b823d4967 100644
> --- a/drivers/platform/chrome/Kconfig
> +++ b/drivers/platform/chrome/Kconfig
> @@ -59,8 +59,9 @@ config CROS_EC_LPC
>            module will be called cros_ec_lpc.
>  
>  config CROS_EC_PROTO
> -        bool
> +        bool "ChromeOS EC communication protocol helpers"
>          help
> -          ChromeOS EC communication protocol helpers.
> +          Say Y here to enable support for the different communication
> +          protocols used to talk with the ChromeOS embedded controller.
>  
>  endif # CHROMEOS_PLATFORMS


  reply	other threads:[~2015-08-18 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  7:15 [PATCH] platform/chrome: Make CROS_EC_PROTO a user selectable option Javier Martinez Canillas
2015-08-18 12:40 ` Bartlomiej Zolnierkiewicz [this message]
2015-08-18 13:02   ` Javier Martinez Canillas
2015-08-18 13:36     ` Bartlomiej Zolnierkiewicz
2015-08-18 13:44       ` Javier Martinez Canillas
2015-08-18 13:54         ` Geert Uytterhoeven
2015-08-18 14:05           ` Javier Martinez Canillas

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=1525696.gQFOjPpKHL@amdc1976 \
    --to=b.zolnierkie@samsung.com \
    --cc=dianders@chromium.org \
    --cc=geert@linux-m68k.org \
    --cc=gwendal@chromium.org \
    --cc=javier@osg.samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sjoerd.simons@collabora.co.uk \
    /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.