From: Nishanth Menon <nm@ti.com>
To: <krzysztof.kozlowski+dt@linaro.org>, <kristo@kernel.org>,
<vigneshr@ti.com>, <mranostay@ti.com>,
<miquel.raynal@bootlin.com>, <robh+dt@kernel.org>
Cc: Nishanth Menon <nm@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: rename clock-names adc_tsc_fck to fck
Date: Thu, 3 Nov 2022 02:23:42 -0500 [thread overview]
Message-ID: <166746020740.2058.2273830543196413507.b4-ty@ti.com> (raw)
In-Reply-To: <20221024151648.394623-1-mranostay@ti.com>
Hi Matt Ranostay,
On Mon, 24 Oct 2022 08:16:48 -0700, Matt Ranostay wrote:
> Avoid the following warnings from dt-schema by just renaming the
> clock-names string from adc_tsc_fck to fck so it matches the values in
> ti,am3359-tscadc.yaml
>
> tscadc@40200000: clock-names:0: 'fck' was expected
>
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: rename clock-names adc_tsc_fck to fck
commit: e5bad300e46c5bd0c5cf0a89c74116fbbf608a8c
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-11-03 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 15:16 [PATCH] arm64: dts: ti: rename clock-names adc_tsc_fck to fck Matt Ranostay
2022-10-28 5:37 ` Gole, Dhruva
2022-11-02 20:14 ` Judith Mendez
2022-11-02 21:32 ` Nishanth Menon
2022-11-03 7:23 ` Nishanth Menon [this message]
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=166746020740.2058.2273830543196413507.b4-ty@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mranostay@ti.com \
--cc=robh+dt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox