From: Krzysztof Kozlowski <krzk@kernel.org>
To: Karthikeyan Krishnasamy <karthikeyan@linumiz.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, alexandre.belloni@bootlin.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 5/8] dt-bindings: rtc: microcrystal,rv3028: add clock-cells property
Date: Tue, 3 Sep 2024 14:51:35 +0200 [thread overview]
Message-ID: <e1513eb7-4ac5-4703-b4ff-2791908f1ec8@kernel.org> (raw)
In-Reply-To: <20240903105245.715899-6-karthikeyan@linumiz.com>
On 03/09/2024 12:52, Karthikeyan Krishnasamy wrote:
> consume clkout from rv3028 rtc which is able to provide
> different clock frequency upon configuration
>
> Signed-off-by: Karthikeyan Krishnasamy <karthikeyan@linumiz.com>
> ---
>
> Notes:
> v2:
> - fix commit message subject
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions, under or above your Signed-off-by tag. Tag is "received", when
provided in a message replied to you on the mailing list. Tools like b4
can help here. However, there's no need to repost patches *only* to add
the tags. The upstream maintainer will do that for tags received on the
version they apply.
https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-03 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 10:52 [PATCH v2 0/8] Add support Relfor Saib board which is based on Rockchip RV1109 SoC Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 1/8] ARM: dts: rockchip: Add i2c3 node for RV1126 Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 2/8] ARM: dts: rockchip: Add i2s0 " Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 3/8] ARM: dts: rockchip: Add pwm " Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 4/8] ARM: dts: rockchip: Add watchdog " Karthikeyan Krishnasamy
2024-09-04 9:11 ` Heiko Stübner
2024-09-04 14:21 ` karthikeyan
2024-09-03 10:52 ` [PATCH v2 5/8] dt-bindings: rtc: microcrystal,rv3028: add clock-cells property Karthikeyan Krishnasamy
2024-09-03 12:51 ` Krzysztof Kozlowski [this message]
2024-09-03 13:29 ` karthikeyan
2024-09-03 14:45 ` Rob Herring
2024-09-04 14:17 ` karthikeyan
2024-09-03 10:52 ` [PATCH v2 6/8] dt-bindings: vendor-prefixes: Add Relfor labs Karthikeyan Krishnasamy
2024-09-03 12:51 ` Krzysztof Kozlowski
2024-09-03 10:52 ` [PATCH v2 7/8] dt-bindings: arm: rockchip: Add Relfor Saib Karthikeyan Krishnasamy
2024-09-03 15:28 ` Rob Herring (Arm)
2024-09-03 10:52 ` [PATCH v2 8/8] ARM: dts: rockchip: Add Relfor Saib board Karthikeyan Krishnasamy
2024-09-04 9:24 ` (subset) [PATCH v2 0/8] Add support Relfor Saib board which is based on Rockchip RV1109 SoC Heiko Stuebner
2024-09-04 14:23 ` karthikeyan
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=e1513eb7-4ac5-4703-b4ff-2791908f1ec8@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=karthikeyan@linumiz.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).