public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Albert Yang <yangzh0906@thundersoft.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: arnd@arndb.de, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	gordon.ge@bst.ai, bst-upstream@bstai.top,
	Albert Yang <yangzh0906@thundersoft.com>
Subject: Re: [PATCH v6 0/2] arm64: dts/defconfig: enable BST C1200 eMMC
Date: Tue, 10 Mar 2026 17:09:21 +0800	[thread overview]
Message-ID: <20260310090921.4169475-1-yangzh0906@thundersoft.com> (raw)
In-Reply-To: <12058c14-67c7-4b43-bbbc-ef0ccb813e61@kernel.org>

On Sun, 01 Mar 2026 14:12:03 +0100, Krzysztof Kozlowski <krzk@kernel.org> wrote:
 
> Please do not send patches to soc@ for review. It is explicitly
> documented - read:
> 
> "The main SoC maintainers can be reached via the alias soc@kernel.org
> only in following cases:
> 
> 1. There are no platform-specific maintainers."
> 
> So are you claiming now that BST is unmaintained? Because if so, we will
> mark it for removal.
> 
> First you send patches for review to the mailing lists. Only then,
> AFTER THE REVIEW, you send them to soc@ list.
> 
> Please read maintainer soc profile.
> 
> Best regards,
> Krzysztof

Understood. BST is maintained. Will resend v7 to the lists for review
first, without soc@.

Best regards,
Albert


      reply	other threads:[~2026-03-10  9:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 10:06 [PATCH v6 0/2] arm64: dts/defconfig: enable BST C1200 eMMC Albert Yang
2026-02-25 10:06 ` [PATCH v6 1/2] arm64: dts: bst: enable eMMC controller in C1200 CDCU1.0 board Albert Yang
2026-02-25 10:06 ` [PATCH v6 2/2] arm64: defconfig: enable BST SDHCI controller Albert Yang
2026-03-01 13:12 ` [PATCH v6 0/2] arm64: dts/defconfig: enable BST C1200 eMMC Krzysztof Kozlowski
2026-03-10  9:09   ` Albert Yang [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=20260310090921.4169475-1-yangzh0906@thundersoft.com \
    --to=yangzh0906@thundersoft.com \
    --cc=arnd@arndb.de \
    --cc=bst-upstream@bstai.top \
    --cc=devicetree@vger.kernel.org \
    --cc=gordon.ge@bst.ai \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox