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] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 20 Dec 2017 00:49:57 -0600
From:   Andy Gross <>
To:     Mathieu Malaterre <>
Cc:     Rob Herring <>, Wei Xu <>,
        Mark Rutland <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Matthias Brugger <>,
        David Brown <>,
        Kees Cook <>,
        Anton Vorontsov <>,
        Colin Cross <>,
        Tony Luck <>,,,,,,
Subject: Re: [PATCH] arm64: dts: Remove leading 0x and 0s from bindings

On Thu, Dec 14, 2017 at 05:53:52PM +0100, Mathieu Malaterre wrote:
> Improve the DTS files by removing all the leading "0x" and zeros to fix the
> following dtc warnings:
> Warning (unit_address_format): Node /XXX unit name should not have leading "0x"
> and
> Warning (unit_address_format): Node /XXX unit name should not have leading 0s
> Converted using the following command:
> find . -type f \( -iname *.dts -o -iname *.dtsi \) -exec sed -E -i -e "s/@0x([0-9a-fA-F\.]+)\s?\{/@\L\1 \{/g" -e "s/@0+([0-9a-fA-F\.]+)\s?\{/@\L\1 \{/g" {} +
> For simplicity, two sed expressions were used to solve each warnings separately.
> To make the regex expression more robust a few other issues were resolved,
> namely setting unit-address to lower case, and adding a whitespace before the
> the opening curly brace:
> This is a follow up to commit 4c9847b7375a ("dt-bindings: Remove leading 0x from bindings notation")
> Reported-by: David Daney <>
> Suggested-by: Rob Herring <>
> Signed-off-by: Mathieu Malaterre <>

Acked-by: Andy Gross <>

Powered by blists - more mailing lists