From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: "Heiko Stübner" <heiko@sntech.de>, "Lee Jones" <lee.jones@linaro.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kernel@vger.kernel.org, Olof Johansson <olof@lixom.net>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH] mfd: fix dependency warning for CHROME_PLATFORMS on !X86, !ARM
Date: Wed, 24 Jun 2015 16:30:04 +0200 [thread overview]
Message-ID: <558ABEEC.3040901@collabora.co.uk> (raw)
In-Reply-To: <1921214.Eo3JuLmrvN@diego>
On 06/24/2015 04:21 PM, Heiko Stübner wrote:
> Am Mittwoch, 24. Juni 2015, 15:17:50 schrieb Lee Jones:
>> On Sun, 21 Jun 2015, Javier Martinez Canillas wrote:
>> > Hello Paul,
>> >
>> > On 06/21/2015 02:01 AM, Paul Gortmaker wrote:
>> > > In commit 062476f24aa7cf714169342cc50626fd9bbb93da ("mfd: cros_ec:
>> > > Move protocol helpers out of the MFD driver") there was a select
>> > > added on CHROME_PLATFORMS, which leads to the following for ppc/mips:
>> > >
>> > > warning: (MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet
>> > > direct dependencies (X86 || ARM)
>> >
>> > Right, sorry for missing that and thank a lot for taking care of it.
>> >
>> > > Presumably the above means MFD_CROS_EC is only currently useful
>> > > on x86 and ARM, so lets limit it to there.
>> >
>> > That is correct, although I wonder if CHROME_PLATFORMS should not
>> > also depend on || COMPILE_TEST and same for MFD_CROS_EC so those
>> > have at least build coverage on other architectures.
>> >
>> > I can't think for a reason to not be buildable on other archs...
>>
>> Right. Will you fix that Javier?
>
Yes, I was waiting to see if Paul agreed and wanted to re-spin his patches
or if anyone else had other opinions.
> looking at the ChromeOS kernel tree (3.18 / oak) it looks like ARM64 might
> also be a nice addition to this list, but I'm not sure if there are more ec
> changes involved.
>
Right, on a second thought I wonder if having CHROME_PLATFORMS depends on
depends on X86 || ARM even makes sense. I see that the individual drivers
already depend on a certain architecture. i.e: CROS_EC_LPC on x86 because
LPC is only found on x86, etc.
So maybe we can just remove the constrain from CHROME_PLATFORMS and let
it be selected on all architectures if someone choose to.
I'll double check and post a patch on top of Paul's tomorrow.
Best regards,
Javier
next prev parent reply other threads:[~2015-06-24 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 0:01 [PATCH] mfd: fix dependency warning for CHROME_PLATFORMS on !X86, !ARM Paul Gortmaker
2015-06-21 0:17 ` Javier Martinez Canillas
2015-06-24 14:17 ` Lee Jones
2015-06-24 14:21 ` Heiko Stübner
2015-06-24 14:30 ` Javier Martinez Canillas [this message]
2015-06-24 14:17 ` Lee Jones
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=558ABEEC.3040901@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=heiko@sntech.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul.gortmaker@windriver.com \
--cc=sameo@linux.intel.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