From: Conor Dooley <conor@kernel.org>
To: gomba007@gmail.com
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
csokas.bence@prolan.hu, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/2] dt-bindings: rtc: Add support for SD2405AL.
Date: Thu, 29 Aug 2024 17:03:58 +0100 [thread overview]
Message-ID: <20240829-reissue-curtsy-3c7c10d0797f@spud> (raw)
In-Reply-To: <20240829-rtc-sd2405al-v6-2-4fbfe2624aa7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
On Thu, Aug 29, 2024 at 01:31:45PM +0200, Tóth János via B4 Relay wrote:
> From: Tóth János <gomba007@gmail.com>
>
> Add the necessary documentation for SD2405AL.
>
> Signed-off-by: Tóth János <gomba007@gmail.com>
> ---
> Documentation/devicetree/bindings/rtc/trivial-rtc.yaml | 2 ++
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
Both of these should really be two different patches, despite how
trivial they would be. If you resubmit, please do that and provide a
link to the vendor in the vendor-prefixes patch. Otherwise,
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
> 2 files changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml b/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> index fffd759c603f..dae594626b2e 100644
> --- a/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> +++ b/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> @@ -38,6 +38,8 @@ properties:
> - dallas,ds1672
> # Extremely Accurate I²C RTC with Integrated Crystal and SRAM
> - dallas,ds3232
> + # SD2405AL Real-Time Clock
> + - dfrobot,sd2405al
> # EM Microelectronic EM3027 RTC
> - emmicro,em3027
> # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index a70ce43b3dc0..bd8b279a5152 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -368,6 +368,8 @@ patternProperties:
> description: Devantech, Ltd.
> "^dfi,.*":
> description: DFI Inc.
> + "^dfrobot,.*":
> + description: DFRobot Corporation
> "^dh,.*":
> description: DH electronics GmbH
> "^difrnce,.*":
>
> --
> 2.34.1
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-08-29 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 11:31 [PATCH v6 0/2] Add support for the DFRobot SD2405AL I2C RTC Module Tóth János via B4 Relay
2024-08-29 11:31 ` [PATCH v6 1/2] drivers: rtc: Add driver for SD2405AL Tóth János via B4 Relay
2024-08-29 11:31 ` [PATCH v6 2/2] dt-bindings: rtc: Add support " Tóth János via B4 Relay
2024-08-29 16:03 ` Conor Dooley [this message]
2024-08-30 7:48 ` Tóth János
2024-08-29 16:17 ` [PATCH v6 0/2] Add support for the DFRobot SD2405AL I2C RTC Module Alexandre Belloni
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=20240829-reissue-curtsy-3c7c10d0797f@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=csokas.bence@prolan.hu \
--cc=devicetree@vger.kernel.org \
--cc=gomba007@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@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