public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Lee Jones <lee.jones@linaro.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Olof Johansson <olof@lixom.net>,
	Doug Anderson <dianders@chromium.org>,
	Bill Richardson <wfrichar@chromium.org>,
	Simon Glass <sjg@google.com>,
	Gwendal Grignou <gwendal@google.com>,
	Stephen Barber <smbarber@chromium.org>,
	Filipe Brandenburger <filbranden@google.com>,
	Todd Broch <tbroch@chromium.org>,
	Alexandru M Stan <amstan@chromium.org>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/7] mfd: cros_ec: add bus-specific proto v3 code
Date: Wed, 27 May 2015 11:06:52 +0200	[thread overview]
Message-ID: <5565892C.8020205@collabora.co.uk> (raw)
In-Reply-To: <20150527085355.GW11677@x1>

Hello Lee,

On 05/27/2015 10:53 AM, Lee Jones wrote:
> On Fri, 22 May 2015, Javier Martinez Canillas wrote:
> 
>> From: Stephen Barber <smbarber@chromium.org>
>> 
>> Add proto v3 support to the SPI, I2C, and LPC.
>> 
>> Signed-off-by: Stephen Barber <smbarber@chromium.org>
>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>> Tested-by: Heiko Stuebner <heiko@sntech.de>
>> Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
>> Tested-by: Gwendal Grignou <gwendal@chromium.org>
>> ---
>> 
>> Changes since v2: None
>> 
>> Changes since v1:
>>  - Added Gwendal Grignou Reviewed-by and Tested-by tags
>> ---
>>  drivers/mfd/cros_ec_i2c.c             | 166 ++++++++++++++-
>>  drivers/mfd/cros_ec_spi.c             | 382 +++++++++++++++++++++++++++++-----
>>  drivers/platform/chrome/cros_ec_lpc.c |  73 ++++++-
>>  include/linux/mfd/cros_ec.h           |   6 +
>>  4 files changed, 569 insertions(+), 58 deletions(-)
> 
> I don't even know what to say; except, 600 lines of grimness!  I tried
> to review, but now my eyes and brain hurt.  I feel sorry for the guys
> who have to actively maintain this stuff.
>

Since I'm not the author of these drivers, it took me some time to
understand them as well. I've been trying to make it more suitable
for upstream and were improved a lot by following your suggestions
(thanks for a lot that!).

> However... you have enough vendor Acks and Tests to make me "happy",
> and if anything is wrong I'm sure you'll come back and fix it
> promptyly.
>

Yes I will and I'm sure that being in mainline will make the code
more maintainable in the long term.

> Acked-by: Lee Jones <lee.jones@linaro.org>
>

Thanks and best regards,
Javier

  reply	other threads:[~2015-05-27  9:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 15:42 [PATCH v3 0/7] mfd: cros_ec: Add multi EC and proto v3 support Javier Martinez Canillas
2015-05-22 15:42 ` [PATCH v3 1/7] mfd: cros_ec: Use a zero-length array for command data Javier Martinez Canillas
2015-05-27  8:36   ` Lee Jones
2015-05-27  8:39     ` Javier Martinez Canillas
2015-05-22 15:42 ` [PATCH v3 2/7] mfd: cros_ec: rev cros_ec_commands.h Javier Martinez Canillas
2015-05-22 15:42 ` [PATCH v3 3/7] mfd: cros_ec: Move protocol helpers out of the MFD driver Javier Martinez Canillas
2015-05-27  8:38   ` Lee Jones
2015-05-22 15:42 ` [PATCH v3 4/7] mfd: cros_ec: add proto v3 skeleton Javier Martinez Canillas
2015-05-27  8:39   ` Lee Jones
2015-05-22 15:42 ` [PATCH v3 5/7] mfd: cros_ec: add bus-specific proto v3 code Javier Martinez Canillas
2015-05-27  8:53   ` Lee Jones
2015-05-27  9:06     ` Javier Martinez Canillas [this message]
2015-05-22 15:42 ` [PATCH v3 6/7] mfd: cros_ec: Support multiple EC in a system Javier Martinez Canillas
2015-05-27  9:11   ` Lee Jones
2015-05-28 14:00     ` Javier Martinez Canillas
2015-05-28 14:26       ` Lee Jones
2015-05-28 14:28         ` Javier Martinez Canillas
2015-05-22 15:42 ` [PATCH v3 7/7] mfd: cros_ec: spi: Add delay for asserting CS Javier Martinez Canillas
2015-05-27  9:14   ` Lee Jones
2015-05-22 19:28 ` [PATCH v3 0/7] mfd: cros_ec: Add multi EC and proto v3 support Heiko Stuebner

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=5565892C.8020205@collabora.co.uk \
    --to=javier.martinez@collabora.co.uk \
    --cc=amstan@chromium.org \
    --cc=dianders@chromium.org \
    --cc=filbranden@google.com \
    --cc=gwendal@google.com \
    --cc=heiko@sntech.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sameo@linux.intel.com \
    --cc=sjg@google.com \
    --cc=smbarber@chromium.org \
    --cc=tbroch@chromium.org \
    --cc=wfrichar@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