From: ben-linux@fluff.org (Ben Dooks)
To: linus-amlogic@lists.infradead.org
Subject: RFC: RTC v5
Date: Mon, 22 Aug 2016 23:14:56 +0100 [thread overview]
Message-ID: <20160822221501.21945-1-ben-linux@fluff.org> (raw)
I've reworked the rtc patches, but have no way of testing them
until I get back from "holiday". Is anyone able to test so that
they can be submitted?
git at github.com:bendooks/amlogic-kenel.git bjdooks/v48-rc3/rtc-v5
next reply other threads:[~2016-08-22 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 22:14 Ben Dooks [this message]
2016-08-22 22:14 ` [PATCH 1/5] rtc: support for amlogic meson rtc Ben Dooks
2016-08-22 22:14 ` [PATCH 2/5] ARM: dts: amlogic: add rtc node for meson8b Ben Dooks
2016-08-22 22:14 ` [PATCH 3/5] meson-rtc: add device-tree binding Ben Dooks
2016-08-22 22:15 ` [PATCH 4/5] ARM: meson: enable RTC for ODRoid-C1 Ben Dooks
2016-08-22 22:15 ` [PATCH 5/5] rtc: warn if rtc_tm_to_time64 overflows in rtc_tm_to_time Ben Dooks
2016-09-07 21:06 ` RFC: RTC v5 Kevin Hilman
2016-09-08 10:21 ` Ben Dooks
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=20160822221501.21945-1-ben-linux@fluff.org \
--to=ben-linux@fluff.org \
--cc=linus-amlogic@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).