linux-kernel - Re: [PATCH 0/3] arm64: dts: ti: k3-j7200: Add support for multiple CAN nodes in J7200

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]

Date: Tue, 6 Feb 2024 14:10:03 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Bhavya
 Kapoor <b-kapoor@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <nm@...com>, <kristo@...nel.org>,
        <robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
        <conor+dt@...nel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/3] arm64: dts: ti: k3-j7200: Add support for multiple CAN nodes in J7200

Hi Bhavya Kapoor,

On Tue, 30 Jan 2024 15:50:41 +0530, Bhavya Kapoor wrote:
> Add CAN Nodes for 18 CAN instances present in main domain and 2 CAN
> instances present in the mcu domain. CAN instance 0 in main domain is
> enabled on transceiver 0 in J7200 SoM. CAN instance 0 and 1 in mcu
> domain and CAN instance 3 in main domain is enabled on transceivers
> 1, 2 and 3 respectively on common processor board.
> 
> Rebased to next-20240130
> 
> [...]

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

[1/3] arm64: dts: ti: k3-j7200: Add support for CAN nodes
      commit: 03b94719ec31ba0e6580f512cba9100bb560e17b
[2/3] arm64: dts: ti: k3-j7200-som-p0: Add support for CAN instance 0 in main domain
      commit: da23e8d1124b93e468a24247021ace34902a9895
[3/3] arm64: dts: ti: k3-j7200: Add support for multiple CAN instances
      commit: 6b80695f93b2253dbf669323154eb06b162f55ef

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
--
Vignesh