From: Rob Herring <robh@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rtc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH 1/2] dt-bindings: rtc: Add TI K3 RTC devicetree bindings documentation
Date: Thu, 14 Apr 2022 10:53:13 -0500 [thread overview]
Message-ID: <YlhDafvp34uv+X5/@robh.at.kernel.org> (raw)
In-Reply-To: <20220412073138.25027-2-nm@ti.com>
On Tue, Apr 12, 2022 at 02:31:37AM -0500, Nishanth Menon wrote:
> This adds the documentation for the devicetree bindings of the Texas
> Instruments RTC modules on K3 family of SoCs such as AM62x SoCs or
> newer.
'devicetree bindings documentation' in the subject is redundant. You
already said that with 'dt-bindings'.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rtc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH 1/2] dt-bindings: rtc: Add TI K3 RTC devicetree bindings documentation
Date: Thu, 14 Apr 2022 10:53:13 -0500 [thread overview]
Message-ID: <YlhDafvp34uv+X5/@robh.at.kernel.org> (raw)
In-Reply-To: <20220412073138.25027-2-nm@ti.com>
On Tue, Apr 12, 2022 at 02:31:37AM -0500, Nishanth Menon wrote:
> This adds the documentation for the devicetree bindings of the Texas
> Instruments RTC modules on K3 family of SoCs such as AM62x SoCs or
> newer.
'devicetree bindings documentation' in the subject is redundant. You
already said that with 'dt-bindings'.
Rob
next prev parent reply other threads:[~2022-04-14 15:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 7:31 [PATCH 0/2] rtc: Introduce rtc-ti-k3 Nishanth Menon
2022-04-12 7:31 ` Nishanth Menon
2022-04-12 7:31 ` [PATCH 1/2] dt-bindings: rtc: Add TI K3 RTC devicetree bindings documentation Nishanth Menon
2022-04-12 7:31 ` Nishanth Menon
2022-04-12 12:06 ` Krzysztof Kozlowski
2022-04-12 12:06 ` Krzysztof Kozlowski
2022-04-12 22:17 ` Nishanth Menon
2022-04-12 22:17 ` Nishanth Menon
2022-04-13 6:42 ` Krzysztof Kozlowski
2022-04-13 6:42 ` Krzysztof Kozlowski
2022-04-13 15:45 ` Nishanth Menon
2022-04-13 15:45 ` Nishanth Menon
2022-04-14 15:53 ` Rob Herring [this message]
2022-04-14 15:53 ` Rob Herring
2022-04-12 7:31 ` [PATCH 2/2] rtc: Introduce ti-k3-rtc Nishanth Menon
2022-04-12 7:31 ` Nishanth Menon
2022-04-14 0:45 ` Andrew Davis
2022-04-14 0:45 ` Andrew Davis
2022-04-15 8:03 ` Vignesh Raghavendra
2022-04-15 8:03 ` Vignesh Raghavendra
2022-04-15 8:14 ` Alexandre Belloni
2022-04-15 8:14 ` 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=YlhDafvp34uv+X5/@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--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=nm@ti.com \
--cc=vigneshr@ti.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.