linux-kernel - Re: [PATCH] arm64: dts: ti: k3-j721e-sk: Remove firmware-name override for R5F

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: <167935261476.210767.15584121281091840384.b4-ty@ti.com>
Date:   Mon, 20 Mar 2023 17:50:33 -0500
From:   Nishanth Menon <nm@...com>
To:     Vignesh Raghavendra <vigneshr@...com>,
        Tero Kristo <kristo@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        <linux-arm-kernel@...ts.infradead.org>, Andrew Davis <afd@...com>
CC:     Nishanth Menon <nm@...com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-j721e-sk: Remove firmware-name override for R5F

Hi Andrew Davis,

On Tue, 07 Mar 2023 12:09:42 -0600, Andrew Davis wrote:
> The firmware name for this core should stay as the default name
> "j7-main-r5f0_0-fw". This is expected to by a symlink to the actual
> firmware file. If one wants to use a different firmware they should
> change where the symlink points. This is usually achieved with
> an update-alternative or other distro specific selection mechanisms.
> 
> The actual selection is policy and does not belong in DT.
> Remove this name override.
> 
> [...]

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

[1/1] arm64: dts: ti: k3-j721e-sk: Remove firmware-name override for R5F
      commit: 22733814631983a8bed09658648f8ffc20b99f69

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