archive mirror
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <>
To: Nishanth Menon <>, Tero Kristo <>,
	Rob Herring <>,
	Krzysztof Kozlowski <>
Cc: Vignesh Raghavendra <>,
Subject: Re: (subset) [PATCH 1/2] arm64: dts: ti: k3-j721e-main: fix RNG node clock id
Date: Thu, 1 Sep 2022 19:59:11 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Daniel Parks,

On Mon, 8 Aug 2022 13:32:00 -0500, Daniel Parks wrote:
> The RNG node for this platform claims pka_in_clk. Change it to claim the
> correct clock x1_clk. [1]
> [1]:

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/2] arm64: dts: ti: k3-j721e-main: fix RNG node clock id
      commit: f42f6f9e77ee6b1b86c006d0436ba303901529a9

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.


linux-arm-kernel mailing list

      parent reply	other threads:[~2022-09-01 14:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 18:32 [PATCH 1/2] arm64: dts: ti: k3-j721e-main: fix RNG node clock id Daniel Parks
2022-08-08 18:32 ` [PATCH 2/2] arm64: dts: ti: k3-am64-main: " Daniel Parks
2022-08-29  7:41   ` Jayesh Choudhary
2022-09-01 14:30   ` Vignesh Raghavendra
2022-08-29  7:44 ` [PATCH 1/2] arm64: dts: ti: k3-j721e-main: " Jayesh Choudhary
2022-09-01 14:29 ` Vignesh Raghavendra [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).