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:   Fri, 28 May 2021 16:42:56 -0500
From:   Nishanth Menon <nm@...com>
To:     Aswath Govindraju <a-govindraju@...com>,
        Andre Przywara <andre.przywara@....com>
CC:     Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
        Grygorii Strashko <grygorii.strashko@...com>,
        Faiz Abbas <faiz_abbas@...com>,
        Lokesh Vutla <lokeshvutla@...com>,
        Rob Herring <robh+dt@...nel.org>, Sekhar Nori <nsekhar@...com>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        Kishon Vijay Abraham I <kishon@...com>,
        Vignesh Raghavendra <vigneshr@...com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j7200: Remove "#address-cells" property from GPIO DT nodes

On Fri, 23 Apr 2021 12:17:57 +0530, Aswath Govindraju wrote:
> GPIO device tree nodes do not have child nodes. Therefore, "#address-cells"
> property should not be added.

Hi Aswath Govindraju,

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

NOTE: I know this adds warnings with W=2 build of dtbs, BUT, just like
xilinx guys[2] and us[33 -> we have already established #address-cells = <0>
make no sense and dtc is still broken as of next-20210528

So, as far as I am concerned, I am going to keep ignoring these kind of
warnings - and "To" Andre as well.. hopefully we can get around to cleaning
this up some day.

Thank you!

[1/1] arm64: dts: ti: k3-j7200: Remove "#address-cells" property from GPIO DT nodes
      commit: 6ec8ba764165f6ecb6f6f7efbfd2ec7ad76dedcb


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/nmenon/linux.git
[2] https://lore.kernel.org/linux-devicetree/CAL_Jsq++DyiKG9smQGx9FAPDJnVrezcXNb0Y5uh-5_2GBzTQpQ@mail.gmail.com/
[3] https://lore.kernel.org/linux-devicetree/20210126163839.57491132@slackpad.fritz.box/
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ