All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Gwendal Grignou <gwendal@chromium.org>,
	Yicheng Li <yichengli@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	"kernel@collabora.com" <kernel@collabora.com>
Subject: Re: [PATCH] mfd: cros_ec: Update cros_ec_commands.h
Date: Wed, 21 Aug 2019 19:27:52 +0200	[thread overview]
Message-ID: <cab6242a-b9a2-ea93-9bfa-a9854949ee8a@collabora.com> (raw)
In-Reply-To: <20190812072832.GO4594@dell>

Hi Lee,

On 12/8/19 9:28, Lee Jones wrote:
> On Mon, 22 Jul 2019, Enric Balletbo i Serra wrote:
> 
>> Hi Lee,
>>
>> On 11/7/19 19:17, Gwendal Grignou wrote:
>>> Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
>>>
>>> Note there is a patch series that move cros_ec_commands.h from
>>> nclude/linux/mfd/ to include/linux/platform_data.
>>>
>>
>> I just sent a new version of the patches mentioned above now that rc1 is out [1]
>>
>> As Gwendal said this patch will conflict with them, so we have two options.
>>
>> 1. If Lee picks that patch I can rebase again my series on top of it.
> 
> Yes please.
> 

Perfect, preparing a new rebased version to send soon.

>> 2. If not, we can wait for Lee reviewing my patch series and then I don't mind
>> to rebase that patch on top of my series and carry the patch through
>> chrome-platform. Anyway I'll need an immutable branch from Lee.
> 
> I just reviewed your series.
> 

Thanks,

Enric

  reply	other threads:[~2019-08-21 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 18:15 [PATCH] mfd: cros_ec: Update cros_ec_commands.h Yicheng Li
2019-07-11 17:17 ` Gwendal Grignou
2019-07-22 14:15   ` Enric Balletbo i Serra
2019-08-12  7:28     ` Lee Jones
2019-08-21 17:27       ` Enric Balletbo i Serra [this message]
2019-08-12  7:27 ` Lee Jones

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=cab6242a-b9a2-ea93-9bfa-a9854949ee8a@collabora.com \
    --to=enric.balletbo@collabora.com \
    --cc=bleung@chromium.org \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=kernel@collabora.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yichengli@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 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.