From: Olof Johansson <olof@lixom.net>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-samsung-soc@vger.kernel.org,
Heiko Stuebner <heiko@sntech.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Gwendal Grignou <gwendal@google.com>,
Doug Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH 1/3] platform/chrome: Don't make CHROME_PLATFORMS depends on X86 || ARM
Date: Tue, 21 Jul 2015 18:29:34 -0700 [thread overview]
Message-ID: <20150722012934.GA12724@localhost> (raw)
In-Reply-To: <1435191645-6022-2-git-send-email-javier.martinez@collabora.co.uk>
On Thu, Jun 25, 2015 at 02:20:42AM +0200, Javier Martinez Canillas wrote:
> The Chrome platform support depends on X86 || ARM because there are
> only Chromebooks using those architectures. But only some drivers
> depend on a given architecture, and the ones that do already have
> a dependency on their specific Kconfig symbol entries.
>
> An option is to also make CHROME_PLATFORMS depends on || COMPILE_TEST
> but is more future proof to remove the dependency and let the drivers
> be built in all architectures if possible to have more build coverage.
>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Acked-by: Olof Johansson <olof@lixom.net>
-Olof
next prev parent reply other threads:[~2015-07-22 1:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 0:20 [PATCH 0/3] mfd: ChromeOS EC Kconfig dependency cleanup Javier Martinez Canillas
2015-06-25 0:20 ` [PATCH 1/3] platform/chrome: Don't make CHROME_PLATFORMS depends on X86 || ARM Javier Martinez Canillas
2015-07-22 1:29 ` Olof Johansson [this message]
2015-07-22 7:16 ` Lee Jones
2015-08-17 7:56 ` Geert Uytterhoeven
2015-08-17 8:36 ` Javier Martinez Canillas
2015-06-25 0:20 ` [PATCH 2/3] mfd: Remove MFD_CROS_EC " Javier Martinez Canillas
2015-06-25 8:38 ` Lee Jones
2015-06-25 8:44 ` Javier Martinez Canillas
2015-06-30 6:09 ` Paul Gortmaker
2015-06-30 6:09 ` Paul Gortmaker
2015-07-22 1:13 ` Paul Gortmaker
2015-07-22 1:13 ` Paul Gortmaker
2015-07-22 1:13 ` Paul Gortmaker
2015-07-22 1:27 ` Javier Martinez Canillas
2015-07-22 1:27 ` Javier Martinez Canillas
2015-07-22 1:31 ` Olof Johansson
2015-07-22 1:31 ` Olof Johansson
2015-07-22 1:30 ` Olof Johansson
2015-07-22 7:15 ` Lee Jones
2015-06-25 0:20 ` [PATCH 3/3] mfd: Remove MFD_CROS_EC_SPI depends on OF Javier Martinez Canillas
2015-06-25 8:38 ` Lee Jones
2015-07-22 7:17 ` Lee Jones
2015-08-07 0:03 ` [PATCH 0/3] mfd: ChromeOS EC Kconfig dependency cleanup Javier Martinez Canillas
2015-08-10 16:10 ` Lee Jones
2015-08-10 16:13 ` Lee Jones
2015-08-10 16:45 ` 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=20150722012934.GA12724@localhost \
--to=olof@lixom.net \
--cc=dianders@chromium.org \
--cc=gwendal@google.com \
--cc=heiko@sntech.de \
--cc=javier.martinez@collabora.co.uk \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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 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.