public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Krzysztof Kozlowski <krzk@kernel•org>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
	Bjorn Andersson <andersson@kernel•org>,
	Andy Gross <agross@kernel•org>,
	Konrad Dybcio <konradybcio@kernel•org>
Subject: Re: Missing signoff in the qcom tree
Date: Thu, 26 Mar 2026 13:56:48 +0000	[thread overview]
Message-ID: <59474ff5-1887-4de3-891d-18b0d37c7493@sirena.org.uk> (raw)
In-Reply-To: <75d0279e-beee-4494-ac29-e1addc45f95c@kernel.org>

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

On Thu, Mar 26, 2026 at 02:52:54PM +0100, Krzysztof Kozlowski wrote:
> On 26/03/2026 14:47, Mark Brown wrote:

> > -next uses it's own contacts list per tree, if there's any updates
> > needed please let me know.  For the qcom tree I currently have:

> Sure, got it. Then for qcom, please switch to:

> Bjorn Andersson <andersson@kernel•org>
> Konrad Dybcio <konradybcio@kernel•org>

> and I think Andy does not need to be Cc-ed anymore.

I've added them - Andy, let me know if you want to be removed (or Bjorn
or Konrad for that matter!).

> Also, I saw that Shawn mentioned about change in imx-mxs - to include:
> Frank Li <Frank.Li@nxp•com>

Someone already let me know about that one.

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

  reply	other threads:[~2026-03-26 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 13:45 Missing signoff in the qcom tree Mark Brown
2026-03-26 13:43 ` Krzysztof Kozlowski
2026-03-26 13:47   ` Mark Brown
2026-03-26 13:52     ` Krzysztof Kozlowski
2026-03-26 13:56       ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-09 11:27 Mark Brown
2026-04-13 16:55 ` Mark Brown
2026-04-20 13:32   ` Mark Brown
2026-03-19 12:06 Mark Brown

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=59474ff5-1887-4de3-891d-18b0d37c7493@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=agross@kernel$(echo .)org \
    --cc=andersson@kernel$(echo .)org \
    --cc=konradybcio@kernel$(echo .)org \
    --cc=krzk@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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