From: Benson Leung <bleung@google.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: wilco_ec: Allow wilco to be compiled in COMPILE_TEST
Date: Thu, 23 Jan 2020 11:44:21 -0800 [thread overview]
Message-ID: <20200123194421.GA38491@google.com> (raw)
In-Reply-To: <20200122012434.88274-1-swboyd@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Hi Stephen,
On Tue, Jan 21, 2020 at 05:24:34PM -0800, Stephen Boyd wrote:
> Enable this Kconfig on COMPILE_TEST enabled configs so we can get more
> build coverage.
>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Applied to our for-next. Thanks!
> ---
> drivers/platform/chrome/wilco_ec/Kconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/chrome/wilco_ec/Kconfig b/drivers/platform/chrome/wilco_ec/Kconfig
> index 365f30e116ee..49e8530ca0ac 100644
> --- a/drivers/platform/chrome/wilco_ec/Kconfig
> +++ b/drivers/platform/chrome/wilco_ec/Kconfig
> @@ -1,7 +1,8 @@
> # SPDX-License-Identifier: GPL-2.0-only
> config WILCO_EC
> tristate "ChromeOS Wilco Embedded Controller"
> - depends on ACPI && X86 && CROS_EC_LPC && LEDS_CLASS
> + depends on X86 || COMPILE_TEST
> + depends on ACPI && CROS_EC_LPC && LEDS_CLASS
> help
> If you say Y here, you get support for talking to the ChromeOS
> Wilco EC over an eSPI bus. This uses a simple byte-level protocol
> --
> Sent by a computer, using git, on the internet
>
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2020-01-23 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 1:24 [PATCH] platform/chrome: wilco_ec: Allow wilco to be compiled in COMPILE_TEST Stephen Boyd
2020-01-23 19:44 ` Benson Leung [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=20200123194421.GA38491@google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.org \
/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