From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: a.zummo@towertech.it, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
Jacky Huang <ychuang570808@gmail.com>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mjchen@nuvoton.com,
schung@nuvoton.com, Jacky Huang <ychuang3@nuvoton.com>
Subject: Re: (subset) [PATCH v4 0/3] Add support for Nuvoton ma35d1 rtc controller
Date: Sun, 17 Dec 2023 23:43:52 +0100 [thread overview]
Message-ID: <170285301016.27693.9578027782544960763.b4-ty@bootlin.com> (raw)
In-Reply-To: <20230925070251.28-1-ychuang570808@gmail.com>
On Mon, 25 Sep 2023 07:02:48 +0000, Jacky Huang wrote:
> From: Jacky Huang <ychuang3@nuvoton.com>
>
> This patch series adds the rtc driver for the nuvoton ma35d1 ARMv8 SoC.
> It includes DT binding documentation, the ma35d1 rtc driver, and device
> tree updates.
>
> The ma35d1 rtc controller provides real-time and calendar messaging
> capabilities. It supports programmable time tick and alarm match
> interrupts. The time and calendar messages are expressed in BCD format.
>
> [...]
Applied, thanks!
[1/3] dt-bindings: rtc: Add Nuvoton ma35d1 rtc
commit: 3767bba698707d7bad5099371b797d0fd6d39709
[3/3] rtc: Add driver for Nuvoton ma35d1 rtc controller
commit: dc0684adf3b6be6b20fec9295027980021d30353
Best regards,
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-12-17 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 7:02 [PATCH v4 0/3] Add support for Nuvoton ma35d1 rtc controller Jacky Huang
2023-09-25 7:02 ` [PATCH v4 1/3] dt-bindings: rtc: Add Nuvoton ma35d1 rtc Jacky Huang
2023-09-25 7:02 ` [PATCH v4 2/3] arm64: dts: nuvoton: Add rtc for ma35d1 Jacky Huang
2023-09-25 7:02 ` [PATCH v4 3/3] rtc: Add driver for Nuvoton ma35d1 rtc controller Jacky Huang
2023-12-17 22:43 ` Alexandre Belloni [this message]
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=170285301016.27693.9578027782544960763.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mjchen@nuvoton.com \
--cc=robh+dt@kernel.org \
--cc=schung@nuvoton.com \
--cc=ychuang3@nuvoton.com \
--cc=ychuang570808@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).