From: Rob Herring <robh@kernel.org>
To: medadyoung@gmail.com
Cc: JJLIU0@nuvoton.com, venture@google.com, avifishman70@gmail.com,
devicetree@vger.kernel.org, YSCHU@nuvoton.com, yuenn@google.com,
ctcchien@nuvoton.com, openbmc@lists.ozlabs.org,
alexandre.belloni@bootlin.com, KFTING@nuvoton.com,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, tali.perry1@gmail.com, KWLIU@nuvoton.com,
a.zummo@towertech.it, tmaimon77@gmail.com,
benjaminfair@google.com
Subject: Re: [PATCH v3 1/3] dt-bindings: rtc: nuvoton: add NCT3018Y Real Time Clock
Date: Wed, 1 Jun 2022 13:51:17 -0500 [thread overview]
Message-ID: <20220601185117.GA215023-robh@kernel.org> (raw)
In-Reply-To: <20220527084647.30835-2-ctcchien@nuvoton.com>
On Fri, 27 May 2022 16:46:45 +0800, medadyoung@gmail.com wrote:
> From: Medad CChien <ctcchien@nuvoton.com>
>
> Document devicetree bindings for the Nuvoton NCT3018Y Real Time Clock.
>
> Signed-off-by: Medad CChien <ctcchien@nuvoton.com>
> ---
> .../bindings/rtc/nuvoton,nct3018y.yaml | 44 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/nuvoton,nct3018y.yaml
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: medadyoung@gmail.com
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
alexandre.belloni@bootlin.com, YSCHU@nuvoton.com,
tmaimon77@gmail.com, KFTING@nuvoton.com, avifishman70@gmail.com,
venture@google.com, openbmc@lists.ozlabs.org, JJLIU0@nuvoton.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
tali.perry1@gmail.com, ctcchien@nuvoton.com,
benjaminfair@google.com, KWLIU@nuvoton.com, a.zummo@towertech.it
Subject: Re: [PATCH v3 1/3] dt-bindings: rtc: nuvoton: add NCT3018Y Real Time Clock
Date: Wed, 1 Jun 2022 13:51:17 -0500 [thread overview]
Message-ID: <20220601185117.GA215023-robh@kernel.org> (raw)
In-Reply-To: <20220527084647.30835-2-ctcchien@nuvoton.com>
On Fri, 27 May 2022 16:46:45 +0800, medadyoung@gmail.com wrote:
> From: Medad CChien <ctcchien@nuvoton.com>
>
> Document devicetree bindings for the Nuvoton NCT3018Y Real Time Clock.
>
> Signed-off-by: Medad CChien <ctcchien@nuvoton.com>
> ---
> .../bindings/rtc/nuvoton,nct3018y.yaml | 44 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/nuvoton,nct3018y.yaml
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
next prev parent reply other threads:[~2022-06-01 18:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:46 [PATCH v3 0/3] RTC: nuvoton: Add nuvoton real time clock driver medadyoung
2022-05-27 8:46 ` medadyoung
2022-05-27 8:46 ` [PATCH v3 1/3] dt-bindings: rtc: nuvoton: add NCT3018Y Real Time Clock medadyoung
2022-05-27 8:46 ` medadyoung
2022-06-01 18:51 ` Rob Herring [this message]
2022-06-01 18:51 ` Rob Herring
2022-05-27 8:46 ` [PATCH v3 2/3] ARM: dts: nuvoton: Add nuvoton RTC3018Y node medadyoung
2022-05-27 8:46 ` medadyoung
2022-05-27 8:46 ` [PATCH v3 3/3] RTC: nuvoton: Add NCT3018Y real time clock driver medadyoung
2022-05-27 8:46 ` medadyoung
2022-06-24 20:26 ` Alexandre Belloni
2022-06-24 20:26 ` Alexandre Belloni
2022-07-07 5:30 ` Medad Young
2022-07-07 5:30 ` Medad Young
2022-07-07 7:17 ` Mining Lin
2022-07-07 7:52 ` Alexandre Belloni
2022-07-07 7:52 ` Alexandre Belloni
2022-07-07 9:36 ` Mining Lin
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=20220601185117.GA215023-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.