public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
	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:21:23 +0200	[thread overview]
Message-ID: <1921214.Eo3JuLmrvN@diego> (raw)
In-Reply-To: <20150624141750.GQ15013@x1>

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?

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.

  reply	other threads:[~2015-06-24 14:21 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 [this message]
2015-06-24 14:30       ` Javier Martinez Canillas
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=1921214.Eo3JuLmrvN@diego \
    --to=heiko@sntech.de \
    --cc=javier.martinez@collabora.co.uk \
    --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