From: Gary Bisson <gary.bisson@boundarydevices.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: devicetree@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
linux-imx@nxp.com, kernel@pengutronix.de,
"Fabio Estevam" <fabio.estevam@nxp.com>,
linux-arm-kernel@lists.infradead.org,
"Lothar Waßmann" <LW@KARO-electronics.de>
Subject: Re: [RFC PATCH] ARM: dts: imx: replace underscore with hyphen in aliases name
Date: Fri, 4 May 2018 09:40:25 +0200 [thread overview]
Message-ID: <20180504074025.GA11186@g751.home> (raw)
In-Reply-To: <1525399128-11587-1-git-send-email-shawnguo@kernel.org>
Hi Shawn,
On Fri, May 04, 2018 at 09:58:48AM +0800, Shawn Guo wrote:
> It replaces underscore with hyphen in aliases name to fix DTC
> alias_paths warning below, which is seen with various i.MX board dts
> files when W=1 switch is on.
>
> Warning (alias_paths): /aliases: aliases property name must include only lowercase and '-'
>
> Cc: Lothar Waßmann <LW@KARO-electronics.de>
> Cc: Gary Bisson <gary.bisson@boundarydevices.com>
> Signed-off-by: Shawn Guo <shawnguo@kernel.org>
> ---
> Hi Lothar, Gary,
>
> Per my search on kernel code, this change will not break anything on
> kernel support. But I'm not really sure about the case of bootloaders
> running on the boards. That's why I'm sending it as RFC.
>
> We really want i.MX to be the first-class citizen in the community.
> After a few cycles efforts on cleaning up DTC warnings, this alias_paths
> warning is the last one we see with i.MX dts files. We really want to
> get rid of it and make i.MX dts be DTC warning free.
>
> So please comment whether we can merge this patch.
Yes that is fine.
Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com>
Thanks,
Gary
next prev parent reply other threads:[~2018-05-04 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 1:58 [RFC PATCH] ARM: dts: imx: replace underscore with hyphen in aliases name Shawn Guo
2018-05-04 6:52 ` Lothar Waßmann
2018-05-04 8:15 ` Shawn Guo
2018-05-04 7:40 ` Gary Bisson [this message]
2018-05-04 8:15 ` Shawn Guo
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=20180504074025.GA11186@g751.home \
--to=gary.bisson@boundarydevices.com \
--cc=LW@KARO-electronics.de \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).