From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 0/5] Add EPSON RX-8571 RTC support
Date: Sat, 2 Mar 2019 22:07:33 +0100 [thread overview]
Message-ID: <20190302210733.GC3452@piout.net> (raw)
In-Reply-To: <1550742048-28068-1-git-send-email-biju.das@bp.renesas.com>
On 21/02/2019 09:40:43+0000, Biju Das wrote:
> This patch set aims to add support for EPSON RX-8571 real-time clock.
> EPSON RX-8571 rtc is compatible with EPSON RX-8581 rtc except that
> former has 16 bytes additional RAM.
>
> 1 byte of nvmem is supported on both RX-8581 and RX-8571. It is
> exposed through sysfs along with support for 16 bytes additional RAM
> present only on EPSON RX-8571.
>
> This patch series is tested against renesas-dev and linux-next.
>
> Biju Das (5):
> rtc: rx8581: Add rx8571 compatible
> rtc: rx8581: Add support for rx8571 RTC
> rtc: rx8581: Add support for Epson rx8571 RTC
Applied 1-3. Note that I squashed 2 and 3 as 2 didn't make much sense
without 3.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-02 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 9:40 [PATCH 0/5] Add EPSON RX-8571 RTC support Biju Das
2019-02-21 9:40 ` [PATCH 1/5] rtc: rx8581: Add rx8571 compatible Biju Das
2019-02-21 9:40 ` [PATCH 5/5] arm64: dts: renesas: r8a774c0-cat874: add RTC support Biju Das
2019-03-01 10:29 ` Geert Uytterhoeven
2019-03-04 9:56 ` Simon Horman
2019-03-02 21:07 ` Alexandre Belloni [this message]
2019-03-04 7:36 ` [PATCH 0/5] Add EPSON RX-8571 " Biju Das
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=20190302210733.GC3452@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=Chris.Paterson2@renesas.com \
--cc=a.zummo@towertech.it \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).