From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Rob Herring <robh+dt@kernel.org>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: <linux-rtc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: rtc: at91: rename rtt bindings file
Date: Tue, 8 Mar 2022 17:40:13 +0100 [thread overview]
Message-ID: <ca66b439-ef3d-9968-7bf7-d0bf5e98813f@microchip.com> (raw)
In-Reply-To: <20220308155735.54146-1-alexandre.belloni@bootlin.com>
On 08/03/2022 at 16:57, Alexandre Belloni wrote:
> atmel,at91sam9-rtc is a confuing name for this file as it is documenting
confusing ^
> the RTT used as an RTC and not the other regular RTC (atmel,at91rm9200-rtc
> and atmel,at91sam9x5-rtc)
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Yes, clearer indeed:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
True that this driver's name was confusing from day 1...
Thanks Alexandre, best regards,
Nicolas
> ---
> .../rtc/{atmel,at91sam9-rtc.yaml => atmel,at91sam9260-rtt.yaml} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename Documentation/devicetree/bindings/rtc/{atmel,at91sam9-rtc.yaml => atmel,at91sam9260-rtt.yaml} (100%)
>
> diff --git a/Documentation/devicetree/bindings/rtc/atmel,at91sam9-rtc.yaml b/Documentation/devicetree/bindings/rtc/atmel,at91sam9260-rtt.yaml
> similarity index 100%
> rename from Documentation/devicetree/bindings/rtc/atmel,at91sam9-rtc.yaml
> rename to Documentation/devicetree/bindings/rtc/atmel,at91sam9260-rtt.yaml
> --
> 2.35.1
>
--
Nicolas Ferre
next prev parent reply other threads:[~2022-03-08 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 15:57 [PATCH] dt-bindings: rtc: at91: rename rtt bindings file Alexandre Belloni
2022-03-08 16:40 ` Nicolas Ferre [this message]
2022-03-09 21:05 ` Rob Herring
2022-03-23 14:39 ` Rob Herring
2022-03-23 19:03 ` 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=ca66b439-ef3d-9968-7bf7-d0bf5e98813f@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=ludovic.desroches@microchip.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).