Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 11 Jun 2020 09:50:04 +0100
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
Message-ID: <20200611085004.GC4671@sirena.org.uk>
References: <1591736054-568-1-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.com>
 <1591736054-568-2-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.com>
 <20200610110810.GD5005@sirena.org.uk>
 <CAMuHMdWCHeSB9mjpdSX_-qxwo33kMb1_1R93CjBtVBPFPKkEOg@mail.gmail.com>
 <20200610164928.GJ5005@sirena.org.uk>
 <CAMuHMdUNo0tMxWsnXi4q8NwubPWHqTvzGOA-0hOr7oo2cRvvUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="QRj9sO5tAVLaXnSD"
Content-Disposition: inline
In-Reply-To: <CAMuHMdUNo0tMxWsnXi4q8NwubPWHqTvzGOA-0hOr7oo2cRvvUg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


--QRj9sO5tAVLaXnSD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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.

--QRj9sO5tAVLaXnSD
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl7h8DwACgkQJNaLcl1U
h9AbHwf+Oh0ZTAsfPJi03Ayhsz+OMqw4Uebch9FIKNb8mGnpo5yZuUA/oMtGTghT
1fT2jkgx+0iNVdRsPz6M1OEuF/ls+JyYrcLOmQyu5Jmb/xhrr62ANmMWQV6oZsD6
9ANB0yKJUixSwYgu6OWeFgmdYmzT4K29839XsSK/rs4Y3ZcRfrF2F5skGbbHzVCE
jtqvXG8+GhJHNXpEtyqOd6+sq19g6wJ/Fh13vas59bKQYKaJnn9pS0mjzEughzJ+
2OQTvE2gAaw4zXf/dKGag1Om1NH6NhS6k8MIxoP/kNa+yyuw2AMSsMt8NC7EsDyy
yXvvE+bPbnlTWD+L8Quyr0M51PRvZA==
=au0+
-----END PGP SIGNATURE-----

--QRj9sO5tAVLaXnSD--