From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Prabhakar <prabhakar.csengg@gmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: spi: renesas,sh-msiof: Add r8a7742 support
Date: Thu, 11 Jun 2020 09:50:04 +0100 [thread overview]
Message-ID: <20200611085004.GC4671@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdUNo0tMxWsnXi4q8NwubPWHqTvzGOA-0hOr7oo2cRvvUg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Wed, Jun 10, 2020 at 09:18:19PM +0200, Geert Uytterhoeven wrote:
> On Wed, Jun 10, 2020 at 6:49 PM Mark Brown <broonie@kernel.org> wrote:
> > I'm much more comfortable explicitly listing the new compatible so that
> > even if someone makes a DT that doesn't bother listing the fallbacks
> > things will work.
> Adding all of them would cause even more churn when adding support for
> a new SoC... There are already more than 700 "renesas," compatible
> values documented that are not directly matched by drivers.
I'm not sure it's a particular concern, especially since you'll be
sending this stuff in the same series as a bindings update and an extra
patch in a series makes very little difference.
> Nowadays we have "make dtbs_check", so if a DTS doesn't conform to the
> binding, it will be flagged.
For things that are upstream.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-11 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 20:54 [PATCH 0/2] Add MSIOF support for R8A7742 SOC Lad Prabhakar
2020-06-09 20:54 ` [PATCH 1/2] dt-bindings: spi: renesas,sh-msiof: Add r8a7742 support Lad Prabhakar
2020-06-10 8:37 ` Geert Uytterhoeven
2020-06-10 11:08 ` Mark Brown
2020-06-10 11:59 ` Geert Uytterhoeven
2020-06-10 16:49 ` Mark Brown
2020-06-10 19:18 ` Geert Uytterhoeven
2020-06-11 8:50 ` Mark Brown [this message]
2020-06-11 12:09 ` Geert Uytterhoeven
2020-06-16 11:03 ` Mark Brown
2020-06-09 20:54 ` [PATCH 2/2] ARM: dts: r8a7742: Add MSIOF[0123] support Lad Prabhakar
2020-06-26 8:53 ` Geert Uytterhoeven
2020-06-15 23:41 ` [PATCH 0/2] Add MSIOF support for R8A7742 SOC Mark Brown
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=20200611085004.GC4671@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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).