devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Mathieu Malaterre <malat@debian.org>, Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
	Heiko Stuebner <heiko@sntech.de>,
	Tony Lindgren <tony@atomide.com>, Sekhar Nori <nsekhar@ti.com>,
	linux-kernel@vger.kernel.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	linux-arm-kernel@axis.com, Baoyou Xie <baoyou.xie@linaro.org>,
	Jason Cooper <jason@lakedaemon.net>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Kevin Hilman <khilman@kernel.org>,
	Viresh Kumar <vireshk@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	linux-rockchip@lists.infradead.org,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Kukjin Kim <kgene@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	Niklas Cassel <niklas.cassel@axis.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	devicetree
Subject: Re: [PATCH 12/25] arm: socfpga: dts: Remove leading 0x and 0s from bindings notation
Date: Thu, 11 Jan 2018 08:38:42 -0600	[thread overview]
Message-ID: <a175eb79-56a1-5bad-9cc0-12fdbbadbaa5@kernel.org> (raw)
In-Reply-To: <20171215111620.20379-12-malat@debian.org>



On 12/15/2017 05:16 AM, 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 -i -e "s/@\([0-9a-fA-FxX\.;:#]+\)\s*{/@\L\1 {/g" -e "s/@0x\(.*\) {/@\1 {/g" -e "s/@0+\(.*\) {/@\1 {/g" {} +^C
> 
> 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:
> 
> https://elinux.org/Device_Tree_Linux#Linux_conventions
> 
> This will solve as a side effect warning:
> 
> Warning (simple_bus_reg): Node /XXX@<UPPER> simple-bus unit address format error, expected "<lower>"
> 
> This is a follow up to commit 4c9847b7375a ("dt-bindings: Remove leading 0x from bindings notation")
> 
> Reported-by: David Daney <ddaney@caviumnetworks.com>
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Mathieu Malaterre <malat@debian.org>
> ---
>  arch/arm/boot/dts/socfpga.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Acked-by: Dinh Nguyen <dinguyen@kernel.org>

Dinh

  reply	other threads:[~2018-01-11 14:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 16:53 [PATCH] arm: dts: Remove leading 0x and 0s from bindings notation Mathieu Malaterre
     [not found] ` <20171214165350.27850-1-malat-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2017-12-15  4:00   ` Viresh Kumar
2017-12-15  8:50   ` Jesper Nilsson
2017-12-15  8:59 ` Krzysztof Kozlowski
2017-12-15 11:19   ` Mathieu Malaterre
2017-12-15 12:18     ` Mathieu Malaterre
     [not found]       ` <CA+7wUsxMdukt2hu+HKua-C5OwSY-yexVgGnkq071yC5A6XX-_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-15 12:41         ` Krzysztof Kozlowski
2017-12-15 11:15 ` [PATCH 01/25] arm: artpec: " Mathieu Malaterre
2017-12-15 11:15   ` [PATCH 02/25] arm: at91/sama: " Mathieu Malaterre
2017-12-15 11:15   ` [PATCH 03/25] arm: bcm: " Mathieu Malaterre
2017-12-15 11:15   ` [PATCH 04/25] arm: exynos/s3c: " Mathieu Malaterre
2017-12-15 11:15   ` [PATCH 05/25] arm: imx: " Mathieu Malaterre
2017-12-26  4:17     ` Shawn Guo
2017-12-15 11:15   ` [PATCH 06/25] arm: integrator: " Mathieu Malaterre
2017-12-15 11:15   ` [PATCH 07/25] arm: keystone: " Mathieu Malaterre
2017-12-15 11:15   ` [PATCH 08/25] arm: lpc32: " Mathieu Malaterre
2017-12-15 11:15   ` [PATCH 09/25] arm: nspire: " Mathieu Malaterre
2017-12-15 11:16   ` [PATCH 10/25] arm: orion5x: " Mathieu Malaterre
2017-12-15 11:16   ` [PATCH 11/25] arm: prima2: " Mathieu Malaterre
2017-12-15 11:16   ` [PATCH 12/25] arm: socfpga: " Mathieu Malaterre
2018-01-11 14:38     ` Dinh Nguyen [this message]
2017-12-15 11:16   ` [PATCH 25/25] arm: ste: " Mathieu Malaterre
  -- strict thread matches above, loose matches on Subject: below --
2017-12-15 12:46 [PATCH 12/25] arm: socfpga: " Mathieu Malaterre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a175eb79-56a1-5bad-9cc0-12fdbbadbaa5@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=alexandre.torgue@st.com \
    --cc=andrew@lunn.ch \
    --cc=baoyou.xie@linaro.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=heiko@sntech.de \
    --cc=jason@lakedaemon.net \
    --cc=jesper.nilsson@axis.com \
    --cc=kgene@kernel.org \
    --cc=khilman@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=malat@debian.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=niklas.cassel@axis.com \
    --cc=nsekhar@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tony@atomide.com \
    --cc=vireshk@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).