From: "'Benson Leung' via rtc-linux" <rtc-linux@googlegroups.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Jonathan Cameron <jic23@kernel.org>,
Lee Jones <lee.jones@linaro.org>,
bleung@chromium.org
Cc: martinez.javier@gmail.com, Guenter Roeck <groeck@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
rtc-linux@googlegroups.com,
Stephen Barber <smbarber@chromium.org>
Subject: [rtc-linux] Re: [PATCH v3 2/4] mfd: cros_ec: Introduce RTC commands and events definitions.
Date: Thu, 13 Jul 2017 13:15:04 -0700 [thread overview]
Message-ID: <9f82780d-47a0-da3f-40ae-8a5ffe9470f2@google.com> (raw)
In-Reply-To: <20170712101309.6045-3-enric.balletbo@collabora.com>
[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]
Hi Enric,
On 07/12/2017 03:13 AM, Enric Balletbo i Serra wrote:
> From: Stephen Barber <smbarber@chromium.org>
>
> The EC can function as a simple RT, this patch adds the RTC related
> definitions needed by the rtc-cros-ec driver.
>
> Signed-off-by: Stephen Barber <smbarber@chromium.org>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Benson Leung <bleung@chromium.org>
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
--
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-07-13 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 10:13 [rtc-linux] [PATCH v3 0/4] mfd: cros-ec: Some fixes and improvements Enric Balletbo i Serra
2017-07-12 10:13 ` [rtc-linux] [PATCH v3 1/4] mfd: cros_ec: Get rid of cros_ec_check_features from cros_ec_dev Enric Balletbo i Serra
2017-07-13 20:33 ` [rtc-linux] " Gwendal Grignou
2017-07-17 10:30 ` Enric Balletbo Serra
2017-07-17 16:37 ` 'Benson Leung' via rtc-linux
2017-07-18 9:19 ` Lee Jones
2017-07-20 6:31 ` Enric Balletbo Serra
2017-07-12 10:13 ` [rtc-linux] [PATCH v3 2/4] mfd: cros_ec: Introduce RTC commands and events definitions Enric Balletbo i Serra
2017-07-13 20:15 ` 'Benson Leung' via rtc-linux [this message]
2017-07-12 10:13 ` [rtc-linux] [PATCH v3 3/4] rtc: cros-ec: add cros-ec-rtc driver Enric Balletbo i Serra
2017-07-13 20:31 ` [rtc-linux] " 'Benson Leung' via rtc-linux
2017-07-12 10:13 ` [rtc-linux] [PATCH v3 4/4] mfd: cros_ec: add RTC as mfd subdevice Enric Balletbo i Serra
2017-07-20 7:15 ` [rtc-linux] " 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=9f82780d-47a0-da3f-40ae-8a5ffe9470f2@google.com \
--to=rtc-linux@googlegroups.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martinez.javier@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox