linux-kernel - Re: [PATCH v2 0/3] Fix reg ranges for main

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: <171826022269.240984.5184847581978215208.b4-ty@ti.com>
Date: Thu, 13 Jun 2024 12:01:22 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <u-kumar1@...com>, <bb@...com>, <devicetree@...r.kernel.org>,
        Jayesh Choudhary <j-choudhary@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <kristo@...nel.org>,
        <robh@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 0/3] Fix reg ranges for main_pktdma dma-controller node

Hi Jayesh Choudhary,

On Tue, 30 Apr 2024 16:22:50 +0530, Jayesh Choudhary wrote:
> The dma-controller node 'main_pktdma' has few memory regions with
> wrong sizes.
> 
> DMASS0_PKTDMA_RINGRT is marked as 4MB region when it is actually a 2MB
> region. Similarly, DMASS0_PKTDMA_TCHANRT is marked as 256KB region but
> the actual size is 128KB as shown in TRM in the section for Main Memory
> Map (Table 2-1)
> 
> [...]

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

[1/3] arm64: dts: ti: k3-am62-main: Fix the reg-range for main_pktdma
      commit: 6edad223553c7f1680fcaca25ded59eba7c6d82d
[2/3] arm64: dts: ti: k3-am62a-main: Fix the reg-range for main_pktdma
      commit: d007a883a61f55b9b195c4c18bbe29de5b802822
[3/3] arm64: dts: ti: k3-am62p-main: Fix the reg-range for main_pktdma
      commit: a6e6604c600aeedf9700de4a55255850391bc3fc

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