linux-kernel - Re: [PATCH 0/5] arm64: dts: ti: k3*: Fix gic-v3 compatible regs

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, 22 Feb 2022 13:31:41 -0600
From:   Nishanth Menon <nm@...com>
To:     Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
        Marc Zyngier <maz@...nel.org>,
        Vignesh Raghavendra <vigneshr@...com>
CC:     Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] arm64: dts: ti: k3*: Fix gic-v3 compatible regs

Hi Nishanth Menon,

On Tue, 15 Feb 2022 14:10:03 -0600, Nishanth Menon wrote:
> This series was triggered by the discussion in [1], and we realized we
> need to cleanup the definitions in K3 SoC. Usage of kvm with gic-v2
> compatibility is a bit niche usecase, but valid and possible with A53
> and A72 even though the GIC500 instantiation is done with no backward
> compatibility.
> 
> Nishanth Menon (5):
>   arm64: dts: ti: k3-am65: Fix gic-v3 compatible regs
>   arm64: dts: ti: k3-j721e: Fix gic-v3 compatible regs
>   arm64: dts: ti: k3-j7200: Fix gic-v3 compatible regs
>   arm64: dts: ti: k3-am64: Fix gic-v3 compatible regs
>   arm64: dts: ti: k3-j721s2: Fix gic-v3 compatible regs
> 
> [...]

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

[1/5] arm64: dts: ti: k3-am65: Fix gic-v3 compatible regs
      commit: 8cae268b70f387ff9e697ccd62fb2384079124e7
[2/5] arm64: dts: ti: k3-j721e: Fix gic-v3 compatible regs
      commit: a06ed27f3bc63ab9e10007dc0118d910908eb045
[3/5] arm64: dts: ti: k3-j7200: Fix gic-v3 compatible regs
      commit: 1a307cc299430dd7139d351a3b8941f493dfa885
[4/5] arm64: dts: ti: k3-am64: Fix gic-v3 compatible regs
      commit: de60edf1be3d42d4a1b303b41c7c53b2f865726e
[5/5] arm64: dts: ti: k3-j721s2: Fix gic-v3 compatible regs
      commit: a966803781fc5e1875511db9392b0d16174c5dd2

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