linux-kernel - Re: [PATCH 0/2] arm64: dts: ti: Update mux-controller node name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <172298005662.488348.14948625003852817425.b4-ty@ti.com>
Date: Tue, 6 Aug 2024 16:34:28 -0500
From: Nishanth Menon <nm@...com>
To: <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        Bhavya
 Kapoor <b-kapoor@...com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <conor+dt@...nel.org>, <krzk+dt@...nel.org>, <robh@...nel.org>,
        <kristo@...nel.org>, <jm@...com>, <vigneshr@...com>
Subject: Re: [PATCH 0/2] arm64: dts: ti: Update mux-controller node name

Hi Bhavya Kapoor,

On Mon, 29 Jul 2024 12:04:09 +0530, Bhavya Kapoor wrote:
> There are 2 mux-controller nodes in J721S2 and J7200 which are
> responsible for transferring can signals to the can phy but same
> node names for both the mux-controllers on a platform led to errors
> while setting up both mux-controllers for can phys simultaneously.
> Thus, update node names for these mux-controller.
> 
> Rebased to next-20240729
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j721s2-som-p0: Update mux-controller node name
      commit: c36f60772e2aeca253924572a9f348ba27192bd0
[2/2] arm64: dts: ti: k3-j7200-som-p0: Update mux-controller node name
      commit: e3cce1229c34b5c28f103361c4d6b3ef17302d5d

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] https://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