Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 12 Jul 2023 10:48:57 +0100
From:   Conor Dooley <conor.dooley@microchip.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
CC:     Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
        <soc@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
        <linux-arm-kernel@lists.infradead.org>,
        <workflows@vger.kernel.org>, <linux-doc@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/process: maintainer-soc: document
 dtbs_check requirement for Samsung
Message-ID: <20230712-skier-ribcage-0d82be7e16fd@wendy>
References: <20230712084131.127982-1-krzysztof.kozlowski@linaro.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="jnDx7med4PR7Ca25"
Content-Disposition: inline
In-Reply-To: <20230712084131.127982-1-krzysztof.kozlowski@linaro.org>
Precedence: bulk

--jnDx7med4PR7Ca25
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 12, 2023 at 10:41:31AM +0200, Krzysztof Kozlowski wrote:
> Samsung ARM/ARM64 SoCs (except legacy S5PV210) are also expected not to
> bring any new dtbs_check warnings.  In fact this have been already
> enforced and tested since few release.
>=20
> Cc: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>=20
> ---

> Not sure where to document this. Creating new maintainer profile for
> Samsung SoC would be an overkill. OTOH, more SoCs might want to grow
> this list, so this also scales poor.

To me, this portion of the document was "information to the
submaintainer", which would be you, not information to the contributors
to the platform. Adding the comment about Samsung SoC seems aimed at
contributors?
I added the bit about W=3D1 on RISC-V since there are multiple
sub-maintainers there.

> ---
>  Documentation/process/maintainer-soc.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>=20
> diff --git a/Documentation/process/maintainer-soc.rst b/Documentation/pro=
cess/maintainer-soc.rst
> index 49f08289d62c..12637530d68f 100644
> --- a/Documentation/process/maintainer-soc.rst
> +++ b/Documentation/process/maintainer-soc.rst
> @@ -133,8 +133,8 @@ with the dt-bindings that describe the ABI.  Please r=
ead the section
>  more information on the validation of devicetrees.
> =20
>  For new platforms, or additions to existing ones, ``make dtbs_check`` sh=
ould not
> -add any new warnings.  For RISC-V, as it has the advantage of being a ne=
wer
> -architecture, ``make dtbs_check W=3D1`` is required to not add any new w=
arnings.
> +add any new warnings.  For RISC-V and Samsung SoC, ``make dtbs_check W=
=3D1`` is
> +required to not add any new warnings.
>  If in any doubt about a devicetree change, reach out to the devicetree
>  maintainers.
> =20
> --=20
> 2.34.1
>=20

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

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

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZK53CQAKCRB4tDGHoIJi
0g01AP9J2DO5r+KESygofbiZ5DRbA3R+nDW85who/mRtjzDaRgD/a2fBQPx9uYgQ
PMTDslMGKoeOXIwmcEChxspAVZkyGwc=
=Mk6D
-----END PGP SIGNATURE-----

--jnDx7med4PR7Ca25--