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>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
	Olof Johansson <olof@lixom.net>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Stephen Barber <smbarber@chromium.org>
Subject: Re: [PATCH v2 3/4] rtc: cros-ec: add cros-ec-rtc driver.
Date: Tue, 14 Feb 2017 09:55:25 +0100	[thread overview]
Message-ID: <c492877b-5bd1-511a-7591-b4ff911ceabc@collabora.com> (raw)
In-Reply-To: <20170123121438.GM16020@dell>

Hi Lee,

On 23/01/17 13:14, Lee Jones wrote:
> On Mon, 23 Jan 2017, Alexandre Belloni wrote:
> 
>> On 19/01/2017 at 13:30:31 +0100, Enric Balletbo i Serra wrote :
>>> From: Stephen Barber <smbarber@chromium.org>
>>>
>>> On platforms with a Chrome OS EC, the EC can function as a simple RTC.
>>> Add a basic driver with this functionality.
>>>
>>> Signed-off-by: Stephen Barber <smbarber@chromium.org>
>>> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
>>
>> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>
>> Lee, this can go through the mfd tree. Hopefully, nobody will add a new
>> driver nearby ;)
> 
> Yes, I can take the set, once all of the Acks are obtained.
> 

Now that the patch series have all the acks, this will finally go through the mfd tree?

I suppose is too late for the upcoming merge window ... so just want to make sure which tree I should monitor to not forget it :)

Thanks,
 Enric

WARNING: multiple messages have this Message-ID (diff)
From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Lee Jones <lee.jones@linaro.org>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
	Olof Johansson <olof@lixom.net>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Stephen Barber <smbarber@chromium.org>
Subject: [rtc-linux] Re: [PATCH v2 3/4] rtc: cros-ec: add cros-ec-rtc driver.
Date: Tue, 14 Feb 2017 09:55:25 +0100	[thread overview]
Message-ID: <c492877b-5bd1-511a-7591-b4ff911ceabc@collabora.com> (raw)
In-Reply-To: <20170123121438.GM16020@dell>

Hi Lee,

On 23/01/17 13:14, Lee Jones wrote:
> On Mon, 23 Jan 2017, Alexandre Belloni wrote:
> 
>> On 19/01/2017 at 13:30:31 +0100, Enric Balletbo i Serra wrote :
>>> From: Stephen Barber <smbarber@chromium.org>
>>>
>>> On platforms with a Chrome OS EC, the EC can function as a simple RTC.
>>> Add a basic driver with this functionality.
>>>
>>> Signed-off-by: Stephen Barber <smbarber@chromium.org>
>>> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
>>
>> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>
>> Lee, this can go through the mfd tree. Hopefully, nobody will add a new
>> driver nearby ;)
> 
> Yes, I can take the set, once all of the Acks are obtained.
> 

Now that the patch series have all the acks, this will finally go through the mfd tree?

I suppose is too late for the upcoming merge window ... so just want to make sure which tree I should monitor to not forget it :)

Thanks,
 Enric



-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2017-02-14  8:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 12:30 [PATCH v2 1/4] mfd: cros_ec: Add helper for event notifier Enric Balletbo i Serra
2017-01-19 12:30 ` [rtc-linux] " Enric Balletbo i Serra
2017-01-19 12:30 ` [PATCH v2 2/4] mfd: cros_ec: Introduce RTC commands and events definitions Enric Balletbo i Serra
2017-01-19 12:30   ` [rtc-linux] " Enric Balletbo i Serra
2017-01-19 12:30 ` [PATCH v2 3/4] rtc: cros-ec: add cros-ec-rtc driver Enric Balletbo i Serra
2017-01-19 12:30   ` [rtc-linux] " Enric Balletbo i Serra
2017-01-22 23:32   ` Alexandre Belloni
2017-01-22 23:32     ` [rtc-linux] " Alexandre Belloni
2017-01-23 12:14     ` Lee Jones
2017-01-23 12:14       ` [rtc-linux] " Lee Jones
2017-02-14  8:55       ` Enric Balletbo i Serra [this message]
2017-02-14  8:55         ` Enric Balletbo i Serra
2017-02-14 15:26         ` Lee Jones
2017-02-14 15:26           ` [rtc-linux] " Lee Jones
2017-02-14 22:18           ` Enric Balletbo i Serra
2017-02-14 22:18             ` [rtc-linux] " Enric Balletbo i Serra
2017-01-19 12:30 ` [PATCH v2 4/4] mfd: cros_ec: add RTC as mfd subdevice Enric Balletbo i Serra
2017-01-19 12:30   ` [rtc-linux] " Enric Balletbo i Serra
2017-01-23 12:14   ` Lee Jones
2017-01-23 12:14     ` [rtc-linux] " Lee Jones
2017-01-23 15:45     ` Enric Balletbo Serra
2017-01-23 15:45       ` [rtc-linux] " Enric Balletbo Serra
2017-01-28  1:11   ` Benson Leung
2017-01-28  1:11     ` [rtc-linux] " Benson Leung

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=c492877b-5bd1-511a-7591-b4ff911ceabc@collabora.com \
    --to=enric.balletbo@collabora.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=rtc-linux@googlegroups.com \
    --cc=smbarber@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.