linux-kernel - Re: [PATCH] arm64: dts: amlogic: c3: fix dtbcheck warning

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: <172526606853.2176850.7789984946561002736.b4-ty@linaro.org>
Date: Mon, 02 Sep 2024 10:34:28 +0200
From: Neil Armstrong <neil.armstrong@...aro.org>
To: Kevin Hilman <khilman@...libre.com>, 
 Jerome Brunet <jbrunet@...libre.com>, 
 Martin Blumenstingl <martin.blumenstingl@...glemail.com>, 
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Xianwei Zhao <xianwei.zhao@...ogic.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] arm64: dts: amlogic: c3: fix dtbcheck warning

Hi,

On Mon, 02 Sep 2024 13:29:39 +0800, Xianwei Zhao wrote:
> Fix warning when use W=1 to build dtb, as following error:
> 
> arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi:65.7-76.4: Warning
> (unit_address_vs_reg): /sram: node has a reg or ranges property,
> but no unit name
> 
> arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi:168.34-413.6: Warning
> (unit_address_vs_reg): /soc/bus@...00000/pinctrl@...0: node has a
> unit name, but no reg or ranges property
> 
> [...]

Thanks, Applied to https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git (v6.12/arm64-dt)

[1/1] arm64: dts: amlogic: c3: fix dtbcheck warning
      https://git.kernel.org/amlogic/c/ca55a30d27cb37c07f58e5c3448f4d19edb1829c

These changes has been applied on the intermediate git tree [1].

The v6.12/arm64-dt branch will then be sent via a formal Pull Request to the Linux SoC maintainers
for inclusion in their intermediate git branches in order to be sent to Linus during
the next merge window, or sooner if it's a set of fixes.

In the cases of fixes, those will be merged in the current release candidate
kernel and as soon they appear on the Linux master branch they will be
backported to the previous Stable and Long-Stable kernels [2].

The intermediate git branches are merged daily in the linux-next tree [3],
people are encouraged testing these pre-release kernels and report issues on the
relevant mailing-lists.

If problems are discovered on those changes, please submit a signed-off-by revert
patch followed by a corrective changeset.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
[3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

-- 
Neil