linux-kernel - Re: [PATCH] arm64: dts: ti: j721e-common-proc-board: Fix sound node-name

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:   Thu, 17 Nov 2022 01:13:37 -0600
From:   Nishanth Menon <nm@...com>
To:     <j-choudhary@...com>, <devicetree@...r.kernel.org>
CC:     Nishanth Menon <nm@...com>, <robh+dt@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <vigneshr@...com>,
        <kristo@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: j721e-common-proc-board: Fix sound node-name

Hi Jayesh Choudhary,

On Wed, 28 Sep 2022 17:55:09 +0530, Jayesh Choudhary wrote:
> If root-node has no reg property, the unit-address should not
> be appended at the end of node-name. sound node has no 'reg'
> property, so remove the unit-address.
> 
> 

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

When I applied, I dropped 'Fixes' tag for a few reasons:
a) It was trivial node cleanup fix, which per stable-rules dont make sense to
   get backported
b) The fixes format itself was wrong
c) The commit on which the fixes were to be applied would'nt apply (There is
   churn since then)

[1/1] arm64: dts: ti: j721e-common-proc-board: Fix sound node-name
      commit: f789fd29650b6fcee8995f53077d03d509a5d9f5

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