From: Kevin Hilman <khilman@baylibre.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
linux-amlogic@lists.infradead.org, rtc-linux@googlegroups.com,
a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
devicetree@vger.kernel.org, narmstrong@baylibre.com,
frowand.list@gmail.com
Subject: [rtc-linux] Re: [PATCH v3 1/4] rtc: support for amlogic meson rtc
Date: Fri, 08 Jul 2016 09:16:30 -0700 [thread overview]
Message-ID: <7hoa6885r5.fsf@baylibre.com> (raw)
In-Reply-To: <1467748122-14833-3-git-send-email-ben.dooks@codethink.co.uk> (Ben Dooks's message of "Tue, 5 Jul 2016 20:48:41 +0100")
Ben Dooks <ben.dooks@codethink.co.uk> writes:
> Add support for the AMLogic meson8b/meson6 RTC block.
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Tested-by: Kevin Hilman <khilman@baylibre.com>
--
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.
next prev parent reply other threads:[~2016-07-08 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 19:48 [rtc-linux] [PATCH v3 0/2] AMLogic Meson SoC RTC driver Ben Dooks
2016-07-05 19:48 ` Ben Dooks
2016-07-05 19:48 ` [rtc-linux] [PATCH v3 1/4] rtc: support for amlogic meson rtc Ben Dooks
2016-07-08 16:16 ` Kevin Hilman [this message]
2016-07-12 17:22 ` [rtc-linux] " Alexandre Belloni
2016-07-12 17:27 ` Ben Dooks
2016-07-12 17:37 ` Alexandre Belloni
2016-07-05 19:48 ` [rtc-linux] [PATCH v3 2/4] meson-rtc: add device-tree binding Ben Dooks
2016-07-13 5:57 ` [rtc-linux] " Frank Rowand
2016-07-13 9:09 ` Ben Dooks
2016-07-13 11:25 ` Mark Rutland
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=7hoa6885r5.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=ben.dooks@codethink.co.uk \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=narmstrong@baylibre.com \
--cc=rtc-linux@googlegroups.com \
/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