linux-kernel - Re: [PATCH v4 0/2] Refactor watchdog instances for j784s4 and j742s2

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: <176841067668.1986622.2045743329581022992.b4-ty@ti.com>
Date: Wed, 14 Jan 2026 11:11:25 -0600
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
	<conor+dt@...nel.org>, <krzk+dt@...nel.org>, Abhash Kumar Jha
	<a-kumar2@...com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<u-kumar1@...com>, <p-mantena@...com>, <m-chawdhry@...com>
Subject: Re: [PATCH v4 0/2] Refactor watchdog instances for j784s4 and j742s2

Hi Abhash Kumar Jha,

On Mon, 12 Jan 2026 14:21:11 +0530, Abhash Kumar Jha wrote:
> This series performs some refactoring around watchdogs for the j784s4
> and j742s2 socs. We have one watchdog per A72 core, hence the number of
> watchdog instances should match the number of A72 cores.
> 
> Move out the extra watchdog instances from the common file and put them
> only in the soc specific file.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j784s4-main.dtsi: Sort the nodes in appropriate order
      commit: 24c9d5fb8bbf5e8c9e6fc2beffeb80ac2da83de4
[2/2] arm64: dts: ti: k3-j784s4-j742s2-main-common.dtsi: Refactor watchdog instances for j784s4
      commit: 61acc4428a7f52e0a13e226ba76f2ce2ca66c065

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
https://ti.com/opensource