From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Jonathan Corbet <corbet@lwn.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: dt: submitting-patches: Document sending DTS patches
Date: Wed, 26 Feb 2025 09:44:41 -0600 [thread overview]
Message-ID: <20250226154441.GA2485697-robh@kernel.org> (raw)
In-Reply-To: <20250225184822.213296-1-krzysztof.kozlowski@linaro.org>
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@linaro.org>
> ---
> .../bindings/submitting-patches.rst | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
I've applied both patches.
Rob
next prev parent reply other threads:[~2025-02-26 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 18:48 [PATCH 1/2] docs: dt: submitting-patches: Document sending DTS patches Krzysztof Kozlowski
2025-02-25 18:48 ` [PATCH 2/2] docs: process: maintainer-soc-clean-dts: linux-next is decisive Krzysztof Kozlowski
2025-02-26 15:29 ` Rob Herring
2025-02-26 21:46 ` Krzysztof Kozlowski
2025-02-25 20:32 ` [PATCH 1/2] docs: dt: submitting-patches: Document sending DTS patches Laurent Pinchart
2025-02-26 15:44 ` Rob Herring [this message]
2025-03-20 17:10 ` patchwork-bot+linux-soc
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=20250226154441.GA2485697-robh@kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--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=soc@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.