The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
	"yangzh0906@thundersoft.com" <yangzh0906@thundersoft.com>
Cc: bst-upstream <bst-upstream@bstai.top>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, "gordon.ge" <gordon.ge@bst.ai>,
	krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
	"Will Deacon" <will@kernel.org>
Subject: Re: [PATCH v8 0/2] arm64: dts/defconfig: enable BST C1200 eMMC
Date: Tue, 02 Jun 2026 14:22:36 +0200	[thread overview]
Message-ID: <24f942db-ec50-4716-9a1b-11ae07923479@app.fastmail.com> (raw)
In-Reply-To: <c6e0a027-38c3-4054-b971-033f021dcff4@kernel.org>

On Tue, Jun 2, 2026, at 14:00, Krzysztof Kozlowski wrote:
> On 02/06/2026 10:43, Albert Yang wrote:
>> 
>> Gentle ping on this series. It has been about 5 weeks since v8 was posted.
>> 
>> The MMC driver patches from the original series were merged via mmc-next
>> in v7.1-rc1. These remaining 2 patches (DTS + defconfig) are still pending.
>> 
>> Both patches have Acked-by: Gordon Ge <gordon.ge@bst.ai>.
>> 
>> No code changes needed — still applies cleanly.
>> 
>> Would you be able to pick this up via soc tree?
>
> This is not a patchset for soc tree. This is patchset for BST - you are
> waiting on BST maintainers. I recommend reading soc maintainer profile
> doc, it describes the process.

What's odd here is that Albert authored and sent all the BST patches
so far, including the one that adds Gordon as the sole maintainer.
I merged these from patches in the initial merge and expected to
see future work get routed through Gordon.

Albert and Gordon, please figure out between yourselves how you
want to handle this in the future. You can both be listed as
maintainers if you want, but to make everybody's life easier,
make sure that only a person who is listed in the MAINTAINERS
files is responsible for collecting patches and forwarding
them to soc@lists.linux.dev for inclusion.

        Arnd

  reply	other threads:[~2026-06-02 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27  6:23 [PATCH v8 0/2] arm64: dts/defconfig: enable BST C1200 eMMC Albert Yang
2026-04-27  6:23 ` [PATCH v8 1/2] arm64: dts: bst: enable eMMC controller in C1200 CDCU1.0 board Albert Yang
2026-04-27  6:23 ` [PATCH v8 2/2] arm64: defconfig: enable BST SDHCI controller Albert Yang
2026-04-27  6:36 ` [PATCH v8 0/2] arm64: dts/defconfig: enable BST C1200 eMMC Krzysztof Kozlowski
2026-04-27  7:46   ` Albert Yang
2026-06-02  8:43 ` Albert Yang
2026-06-02 12:00   ` Krzysztof Kozlowski
2026-06-02 12:22     ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-27  6:23 Albert Yang
2026-04-27  5:55 Albert Yang

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=24f942db-ec50-4716-9a1b-11ae07923479@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=bst-upstream@bstai.top \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gordon.ge@bst.ai \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=will@kernel.org \
    --cc=yangzh0906@thundersoft.com \
    /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