From: Johan Hovold <johan@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Barry Song <Baohua.Song@csr.com>, Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 0/3] ARM: dts: atlas7: fix spaces in compatible strings
Date: Thu, 12 Mar 2020 12:27:24 +0100 [thread overview]
Message-ID: <20200312112724.GP14211@localhost> (raw)
In-Reply-To: <20200212104348.19940-1-johan@kernel.org>
On Wed, Feb 12, 2020 at 11:43:45AM +0100, Johan Hovold wrote:
> I stumbled over a new driver in 5.6 whose compatible strings did not
> match the corresponding binding due to spaces in the driver compatible
> strings:
>
> https://lkml.kernel.org/r/20200212092426.24012-1-johan@kernel.org
>
> A quick grep revealed that we a couple of devicetrees in mainline with
> similarly malformed compatible strings.
>
> Note that there are no in-kernel drivers or bindings that use the
> strings question, so I think simply dropping the spaces would be
> acceptable. This is especially true for the flexnox nodes that also
> specify "simple-bus" so therefore I split the fixes in three patches.
No reply from the CSR people after a month.
Rob, could you pick these up directly?
Johan
> Johan Hovold (3):
> ARM: dts: atlas7: fix space in flexnoc compatible strings
> ARM: dts: atlas7: fix space in gmac compatible string
> ARM: dts: atlas7: fix space in g2d compatible string
>
> arch/arm/boot/dts/atlas7.dtsi | 30 +++++++++++++++---------------
> 1 file changed, 15 insertions(+), 15 deletions(-)
prev parent reply other threads:[~2020-03-12 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 10:43 [PATCH 0/3] ARM: dts: atlas7: fix spaces in compatible strings Johan Hovold
2020-02-12 10:43 ` [PATCH 1/3] ARM: dts: atlas7: fix space in flexnoc " Johan Hovold
2020-02-12 10:43 ` [PATCH 2/3] ARM: dts: atlas7: fix space in gmac compatible string Johan Hovold
2020-02-12 10:43 ` [PATCH 3/3] ARM: dts: atlas7: fix space in g2d " Johan Hovold
2020-03-12 11:27 ` Johan Hovold [this message]
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=20200312112724.GP14211@localhost \
--to=johan@kernel.org \
--cc=Baohua.Song@csr.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).