workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Date: Wed, 12 Jul 2023 10:48:57 +0100	[thread overview]
Message-ID: <20230712-skier-ribcage-0d82be7e16fd@wendy> (raw)
In-Reply-To: <20230712084131.127982-1-krzysztof.kozlowski@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]

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.
> 
> Cc: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> 
> ---

> 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=1 on RISC-V since there are multiple
sub-maintainers there.

> ---
>  Documentation/process/maintainer-soc.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/process/maintainer-soc.rst b/Documentation/process/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 read the section
>  more information on the validation of devicetrees.
>  
>  For new platforms, or additions to existing ones, ``make dtbs_check`` should not
> -add any new warnings.  For RISC-V, as it has the advantage of being a newer
> -architecture, ``make dtbs_check W=1`` is required to not add any new warnings.
> +add any new warnings.  For RISC-V and Samsung SoC, ``make dtbs_check W=1`` is
> +required to not add any new warnings.
>  If in any doubt about a devicetree change, reach out to the devicetree
>  maintainers.
>  
> -- 
> 2.34.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-07-12  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  8:41 Krzysztof Kozlowski
2023-07-12  9:48 ` Conor Dooley [this message]
2023-07-12 11:46   ` Krzysztof Kozlowski
2023-07-12 12:34     ` Conor Dooley
2023-07-12 19:37       ` Krzysztof Kozlowski

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=20230712-skier-ribcage-0d82be7e16fd@wendy \
    --to=conor.dooley@microchip.com \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    --cc=workflows@vger.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