From: Andreas Kemnade <andreas@kemnade.info>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Lucas Stach <lst@pengutronix.de>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
robh+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v2 4/5] ARM: dts: imx6sl: fix mmc compatibles
Date: Tue, 28 Sep 2021 08:51:19 +0200 [thread overview]
Message-ID: <20210928085119.51547f2c@aktux> (raw)
In-Reply-To: <CA+Eumj50L-bbVBX99Q-6y1-o_R58JvJFsStck+O2-18qJSUT1g@mail.gmail.com>
Hi,
On Mon, 27 Sep 2021 09:34:57 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> wrote:
> On Sun, 26 Sept 2021 at 20:33, Andreas Kemnade <andreas@kemnade.info> wrote:
> >
> > Hi Ahmad,
> >
> > On Sun, 26 Sep 2021 08:54:35 +0200
> > Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> >
> > > Hello Andreas,
> > >
> > > On 24.09.21 11:14, Andreas Kemnade wrote:
> > > > Binding specification only allows one compatible here.
> > >
> > > This same change was NACKed by Lucas here:
> > > https://lore.kernel.org/linux-devicetree/72e1194e10ccb4f87aed96265114f0963e805092.camel@pengutronix.de/
> > >
> > > I also think the schema should be fixed instead.
> > >
> > well, that argumentation makes sense. Feel free to drop this patch. I
> > will not repost the series if it is just about dropping patches.
>
> The argument of using a new DTB with an old kernel, therefore
> prohibiting changes in new DTB, does not make that much sense, except
> when caring about other systems which would like to directly reuse the
> DTB... anyway it's not that important to fight over it.
>
well, I have no strong opinion here, but I want to get rid of that
warning, unecessary noise which might hide real problems.
Regards,
Andreas
next prev parent reply other threads:[~2021-09-28 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 9:14 [PATCH v2 0/5] ARM: dts: imx6sl / imx6sll: dtbs_check errors Andreas Kemnade
2021-09-24 9:14 ` [PATCH v2 1/5] ARM: dts: imx: e60k02: correct led node name Andreas Kemnade
2021-09-24 9:14 ` [PATCH v2 2/5] ARM: dts: imx6sl: fixup of operating points Andreas Kemnade
2021-09-24 9:14 ` [PATCH v2 3/5] ARM: dts: imx6sll: " Andreas Kemnade
2021-09-24 9:14 ` [PATCH v2 4/5] ARM: dts: imx6sl: fix mmc compatibles Andreas Kemnade
2021-09-26 6:54 ` Ahmad Fatoum
2021-09-26 18:33 ` Andreas Kemnade
2021-09-27 7:34 ` Krzysztof Kozlowski
2021-09-28 6:51 ` Andreas Kemnade [this message]
2023-01-07 16:39 ` Andreas Kemnade
2021-09-24 9:14 ` [PATCH v2 5/5] ARM: dts: imx6sll: " Andreas Kemnade
2021-10-05 5:46 ` [PATCH v2 0/5] ARM: dts: imx6sl / imx6sll: dtbs_check errors 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=20210928085119.51547f2c@aktux \
--to=andreas@kemnade.info \
--cc=a.fatoum@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lst@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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).