From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Olof Johansson <olof@lixom.net>,
Doug Anderson <dianders@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/chrome: Make CROS_EC_PROTO a user selectable option
Date: Tue, 18 Aug 2015 16:05:20 +0200 [thread overview]
Message-ID: <55D33BA0.1090502@osg.samsung.com> (raw)
In-Reply-To: <CAMuHMdWmZ1NU2r2LaCAQm176dOtP-TR0DeYiM0HJRJvCzhrpbQ@mail.gmail.com>
Hello Geert,
On 08/18/2015 03:54 PM, Geert Uytterhoeven wrote:
> Hi Javier,
>
> On Tue, Aug 18, 2015 at 3:44 PM, Javier Martinez Canillas
> <javier@osg.samsung.com> wrote:
>>>> Yes, the original Kconfig warning message was:
>>>>
>>>> warning: (MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet direct dependencies (X86 || ARM)
>>>>
>>>> Paul fixed on [0] by making MFD_CROS_EC depends on X86 || ARM but that
>>>> is not really true since the driver could be used in other platforms so
>>>> I tried to instead fix it by removing unneeded dependencies in [1] but
>>>> one of the patches was nacked by Geert [2] who mentioned the issue about
>>>> mixing select and "depends on".
>>>
>>> I think that Geert's comments are valid. Dependencies should limit
>>> the config option to the archs for which the driver is really needed
>>> (the rest can be handled with COMPILE_TEST dependency).
>>>
>>
>> Yes, which is true for the drivers under CHROME_PLATFORMS (i.e: CROS_EC_LPC
>> has X86 || COMPILE_TEST) but my point was that CHROME_PLATFORMS is not a
>> driver but a submenu that has (for now) drivers for ARM and X86. But that
>> doesn't mean that a Chromebook for another arch could be produced and then
>> you will need to add a X86 || ARM || FOO || BAR || COMPILE_TEST for
>> CHROME_PLATFORMS which seems to me kind of silly.
>
> However, that's usually the way it is done: such a dependency is added to
> prevent the question from showing up on platforms where it doesn't make
> sense.
>
> If the drivers become needed on other platforms, the dependency can be
> relaxed.
>
Ok, I'll reintroduce the arch dependency for CHROME_PLATFORMS then
and add a || COMPILE_TEST.
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
prev parent reply other threads:[~2015-08-18 14:05 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
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 [this message]
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=55D33BA0.1090502@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=dianders@chromium.org \
--cc=geert@linux-m68k.org \
--cc=gwendal@chromium.org \
--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.