public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: soc@kernel.org
Subject: Re: [PATCH 1/2] Documentation/process: maintainer-soc: Trim from trivial ask-DT
Date: Mon, 20 Apr 2026 15:59:28 +0000	[thread overview]
Message-ID: <177670076856.1706382.6071437791637463585.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260413074401.27282-3-krzysztof.kozlowski@oss.qualcomm.com>

Hello:

This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Mon, 13 Apr 2026 09:44:02 +0200 you wrote:
> It is obvious that one can ask DT maintainers of something, just like
> one can ask anyone, so just drop the sentence.  Concise documents with
> rules have bigger chances of actually being read by people.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
>  Documentation/process/maintainer-soc.rst | 2 --
>  1 file changed, 2 deletions(-)

Here is the summary with links:
  - [1/2] Documentation/process: maintainer-soc: Trim from trivial ask-DT
    https://git.kernel.org/soc/soc/c/f325b239a7bb
  - [2/2] Documentation/process: maintainer-soc: Document purpose of defconfigs
    https://git.kernel.org/soc/soc/c/8b0beb45840a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-04-20 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  7:44 [PATCH 1/2] Documentation/process: maintainer-soc: Trim from trivial ask-DT Krzysztof Kozlowski
2026-04-13  7:44 ` [PATCH 2/2] Documentation/process: maintainer-soc: Document purpose of defconfigs Krzysztof Kozlowski
2026-04-20 15:59 ` 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=177670076856.1706382.6071437791637463585.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --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