From: patchwork-bot+linux-soc@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: soc@kernel.org
Subject: Re: [PATCH 1/2] docs: dt: submitting-patches: Document sending DTS patches
Date: Thu, 20 Mar 2025 17:10:41 +0000 [thread overview]
Message-ID: <174249064199.1843567.5989329978132836009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250225184822.213296-1-krzysztof.kozlowski@linaro.org>
Hello:
This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Tue, 25 Feb 2025 19:48:21 +0100 you 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.
>
> [...]
Here is the summary with links:
- [1/2] docs: dt: submitting-patches: Document sending DTS patches
https://git.kernel.org/soc/soc/c/d98d35d99e0f
- [2/2] docs: process: maintainer-soc-clean-dts: linux-next is decisive
https://git.kernel.org/soc/soc/c/a42d2d53a6d7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-20 17:10 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
2025-03-20 17:10 ` patchwork-bot+linux-soc [this message]
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=174249064199.1843567.5989329978132836009.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=soc@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