From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Brian Norris <briannorris@chromium.org>,
Lee Jones <lee.jones@linaro.org>
Cc: Olof Johansson <olof@lixom.net>,
linux-kernel@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH] mfd: cros_ec: allow building for ARM64
Date: Mon, 11 Apr 2016 13:15:56 -0400 [thread overview]
Message-ID: <570BDBCC.9060502@osg.samsung.com> (raw)
In-Reply-To: <20160411164209.GA11034@localhost>
Hello Brian,
On 04/11/2016 12:42 PM, Brian Norris wrote:
> On Mon, Apr 11, 2016 at 09:48:49AM +0100, Lee Jones wrote:
>> When submitting patches, please use the format appropriate for the
>> subsystem.
>>
>> `git log --oneline -- <subsystem>` helps with this.
>
> $ git log --oneline --no-merges drivers/mfd/cros_ec*.c | head -10
> 8827a642a463 mfd: cros_ec_spi: Repair comparison ordering issue
> 2756db6c6366 mfd: cros_ec_i2c: Fix trivial 'tabs before spaces'
> whitespace issue.
> 6d6e44a95316 mfd: cros ec: Lock the SPI bus while holding chipselect
> 3821a065f567 spi: Drop owner assignment from spi_drivers
> 385c0012dfa0 mfd: cros_ec_i2c: Add OF match table
> a78ea195f77a mfd: cros_ec: spi: Add OF match table
> 0e777366fb0e mfd: Drop owner assignment from i2c_drivers
> cf649e00769a mfd: cros_ec: Staticise some newly introduced structures
> ff4378f4b813 mfd: cros_ec: spi: Add delay for asserting CS
> 57b33ff077be mfd: cros_ec: Support multiple EC in a system
>
> So...what's the problem with the subject?
>
I also don't see what's wrong with the subject line...
>> 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.
>
> I can add a short description. But there's really not much more to it
> than the subject. We have ARM64 platforms we want to use this on. Some
> are already released, and some are in development.
>
I think at least a short description is always welcomed. Even if the
patch is obvious, it should state why the change was introduced.
> Brian
>
>>> 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.
Patch looks good to me, so after resending with a commit message:
Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-04-11 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 20:11 Brian Norris
2016-04-11 8:48 ` Lee Jones
2016-04-11 16:42 ` Brian Norris
2016-04-11 17:15 ` Javier Martinez Canillas [this message]
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=570BDBCC.9060502@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=briannorris@chromium.org \
--cc=computersforpeace@gmail.com \
--cc=lee.jones@linaro.org \
--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
Powered by JetHome