linux-kernel - Re: [PATCH v2 0/3] arm64: dts: ti: k3: Add additioal regs for DMA components

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: <170266081594.3490039.10351809799939114334.b4-ty@ti.com>
Date: Fri, 15 Dec 2023 11:20:26 -0600
From: Nishanth Menon <nm@...com>
To: Tero Kristo <kristo@...nel.org>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Vignesh Raghavendra <vigneshr@...com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <j-luthra@...com>
Subject: Re: [PATCH v2 0/3] arm64: dts: ti: k3: Add additioal regs for DMA components

Hi Vignesh Raghavendra,

On Wed, 13 Dec 2023 19:21:35 +0530, Vignesh Raghavendra wrote:
> This adds additional reg ranges which are not directly used by Linux but
> by other components like U-Boot
> 
> Binding is accepted via dmaengine tree and is in linux-next[0]
> 
> [0] https://lore.kernel.org/dmaengine/170083278148.771517.1841889156174413563.b4-ty@kernel.org/
> 
> [...]

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

[1/3] arm64: dts: ti: k3-am65: Add additional regs for DMA components
      commit: 0fa8d3a5eb8e737726a3c7376222ee40fae1988d
[2/3] arm64: dts: ti: k3-j7*: Add additional regs for DMA components
      commit: 1b62a3cfddbb5664bc4360b3cb0d76b9b99abdc5
[3/3] arm64: dts: ti: k3-am6*: Add additional regs for DMA components
      commit: 7643f7ebcbc723e682d22c207ac35b41d7248650

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