[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250226154441.GA2485697-robh@kernel.org>
Date: Wed, 26 Feb 2025 09:44:41 -0600
From: Rob Herring <robh@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Jonathan Corbet <corbet@....net>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
soc@...ts.linux.dev, workflows@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/2] docs: dt: submitting-patches: Document sending DTS
patches
On Tue, Feb 25, 2025 at 07:48:21PM +0100, Krzysztof Kozlowski wrote:
> Document two rules already widely used and enforced by DT maintainers
> and SoC platform maintainers:
>
> 1. DTS patches should be placed at the end of driver patchset to
> indicate no dependencies of driver code on DTS.
>
> 2. DTS patches should be applied via SoC platform maintainers, because
> it is a driver-independent hardware description. However some
> driver maintainers are reluctant to pick up portions of patchsets and
> prefer to take entire set at once. For such cases, the DTS portion
> should be split into separate patchset, so it will not end up in the
> driver subsystem integration tree.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> ---
> .../bindings/submitting-patches.rst | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
I've applied both patches.
Rob
Powered by blists - more mailing lists