Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Nishanth Menon <nm@ti.com>
To:     <vigneshr@ti.com>, <j-choudhary@ti.com>
CC:     Nishanth Menon <nm@ti.com>, <linux-arm-kernel@lists.infradead.org>,
        <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
        <j-keerthy@ti.com>, <s-anna@ti.com>,
        <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
        <afd@ti.com>, <kristo@kernel.org>
Subject: Re: [PATCH v2 0/3] RNG clock property cleanup
Date:   Thu, 17 Nov 2022 01:16:45 -0600
Message-ID: <166866922717.18115.2072838771228935448.b4-ty@ti.com>
In-Reply-To: <20221107110607.59216-1-j-choudhary@ti.com>
References: <20221107110607.59216-1-j-choudhary@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Jayesh Choudhary,

On Mon, 7 Nov 2022 16:36:04 +0530, Jayesh Choudhary wrote:
> This series removes the clock property from the rng node of
> K3 devices for TI SoCs as that clock is not dedicated to RNG
> module and it cannot be controlled by the rng driver.
> 
> DT binding fix:
> <https://lore.kernel.org/all/20220901171041.32056-1-afd@ti.com/>
> 
> [...]

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

Couple of minor things:
a) cover letter suggestion: for the usual arm64: dts: ti: ... convention - it
  is useful for folks who are'nt aware to understand which subsystem the series
  goes to..
b) Follow the stable-rules for using Fixes or not. I chose to drop it since it
   serves no functional purpose anyways (and I would'nt call a regression esp
   on a disabled node).

[1/3] arm64: dts: ti: k3-am65-main: drop RNG clock
      commit: cfc75a93d7256d65c7b463620e7c13bd8219707b
[2/3] arm64: dts: ti: k3-j721e-main: drop RNG clock
      commit: a315097a23eb1976e8eac397c02ada82618858bb
[3/3] arm64: dts: ti: k3-am64-main: drop RNG clock
      commit: c1e56c8250a234d9bcd9e2f060da229688dfd9eb

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