From: Lee Jones <lee.jones@linaro.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Olof Johansson <olof@lixom.net>,
linux-kernel@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: [PATCH] mfd: cros_ec: allow building for ARM64
Date: Mon, 11 Apr 2016 09:48:49 +0100 [thread overview]
Message-ID: <20160411084849.GK4592@x1> (raw)
In-Reply-To: <1460146297-32535-1-git-send-email-briannorris@chromium.org>
When submitting patches, please use the format appropriate for the
subsystem.
`git log --oneline -- <subsystem>` helps with this.
Also please provide a commit log containing a short description of the
change. Are you enabling ARM64 becuase the driver is able to be used
on a new platform? If not, how did this work before? Etc.
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> ---
> drivers/mfd/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index eea61e349e26..1d63c5fb3f3c 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -134,7 +134,7 @@ config MFD_CROS_EC
> select MFD_CORE
> select CHROME_PLATFORMS
> select CROS_EC_PROTO
> - depends on X86 || ARM || COMPILE_TEST
> + depends on X86 || ARM || ARM64 || COMPILE_TEST
> help
> If you say Y here you get support for the ChromeOS Embedded
> Controller (EC) providing keyboard, battery and power services.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-04-11 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 20:11 [PATCH] mfd: cros_ec: allow building for ARM64 Brian Norris
2016-04-11 8:48 ` Lee Jones [this message]
2016-04-11 16:42 ` Brian Norris
2016-04-11 17:15 ` Javier Martinez Canillas
2016-04-12 7:13 ` Lee Jones
2016-04-12 13:54 ` 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=20160411084849.GK4592@x1 \
--to=lee.jones@linaro.org \
--cc=briannorris@chromium.org \
--cc=computersforpeace@gmail.com \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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;
as well as URLs for NNTP newsgroup(s).