From: Rob Herring <robh@kernel.org>
To: Medad CChien <medadyoung@gmail.com>
Cc: benjaminfair@google.com, alexandre.belloni@bootlin.com,
a.zummo@towertech.it, avifishman70@gmail.com,
ctcchien@nuvoton.com, devicetree@vger.kernel.org,
tali.perry1@gmail.com, yuenn@google.com, KWLIU@nuvoton.com,
openbmc@lists.ozlabs.org, KFTING@nuvoton.com, JJLIU0@nuvoton.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
YSCHU@nuvoton.com, tmaimon77@gmail.com, venture@google.com,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dt-bindings: rtc: nuvoton: add NCT3018Y Real Time Clock
Date: Tue, 17 May 2022 20:19:37 -0500 [thread overview]
Message-ID: <20220518011937.GA2012974-robh@kernel.org> (raw)
In-Reply-To: <20220517092927.19537-3-ctcchien@nuvoton.com>
On Tue, 17 May 2022 17:29:25 +0800, Medad CChien wrote:
> Document devicetree bindings for the Nuvoton NCT3018Y Real Time Clock.
>
> Signed-off-by: Medad CChien <ctcchien@nuvoton.com>
> ---
> .../bindings/rtc/nuvoton,nct3018y.yaml | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/nuvoton,nct3018y.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-05-18 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 9:29 [PATCH v2 0/3] RTC: nuvoton: Add nuvoton real time clock driver Medad CChien
2022-05-17 9:29 ` [PATCH v2 1/3] ARM: dts: nuvoton: Add nuvoton RTC3018Y node Medad CChien
2022-05-17 9:29 ` [PATCH v2 2/3] dt-bindings: rtc: nuvoton: add NCT3018Y Real Time Clock Medad CChien
2022-05-18 1:19 ` Rob Herring [this message]
2022-05-18 3:12 ` Medad Young
2022-05-17 9:29 ` [PATCH v2 3/3] RTC: nuvoton: Add NCT3018Y real time clock driver Medad CChien
2022-05-17 19:11 ` Alexandre Belloni
2022-05-18 3:11 ` Medad Young
2022-05-18 8:28 ` Alexandre Belloni
2022-05-23 8:59 ` Medad Young
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=20220518011937.GA2012974-robh@kernel.org \
--to=robh@kernel.org \
--cc=JJLIU0@nuvoton.com \
--cc=KFTING@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=YSCHU@nuvoton.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=ctcchien@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=medadyoung@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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 NNTP newsgroup(s).