From: Krzysztof Kozlowski <krzk@kernel.org>
To: Albert Yang <yangzh0906@thundersoft.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
ulf.hansson@linaro.org, catalin.marinas@arm.com, will@kernel.org,
arnd@arndb.de, adrian.hunter@intel.com, robin.murphy@arm.com,
ding.wang@bst.ai, gordon.ge@bst.ai
Cc: bst-upstream@bstai.top, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-mmc@vger.kernel.org,
soc@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 8/8] MAINTAINERS: add and consolidate Black Sesame Technologies (BST) ARM SoC support
Date: Tue, 12 Aug 2025 15:33:29 +0200 [thread overview]
Message-ID: <45ec2fee-9b76-4f36-8476-000fbce775c6@kernel.org> (raw)
In-Reply-To: <20250812123110.2090460-9-yangzh0906@thundersoft.com>
On 12/08/2025 14:31, Albert Yang wrote:
> Add and consolidate the MAINTAINERS entry for Black Sesame Technologies
I do not see consolidation in the patch, so this part and subject are
incorrect. You only add.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
> ARM SoC support. This entry covers device tree bindings, drivers, and board
> files for BST SoCs, including MMC, and platform support.
>
> Signed-off-by: Ge Gordon <gordon.ge@bst.ai>
What does this SoB represent? Who wrote the code?
You added that SoB everywhere so I have worries it was automatic or
manager's decision. That isn't what SoB is about.
And looking at actual M: entry, this should be rather publicly Acked.
That's what Ack is. Not SoB.
> Signed-off-by: Albert Yang <yangzh0906@thundersoft.com>
> ---
> Change for v3:
> - No changes
>
> Change for v2:
> - No changes
> ---
> MAINTAINERS | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index efb51ee92683..e3236384c28a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2441,6 +2441,16 @@ S: Maintained
> F: Documentation/devicetree/bindings/arm/blaize.yaml
> F: arch/arm64/boot/dts/blaize/
>
> +ARM/BST SOC SUPPORT
> +M: Ge Gordon <gordon.ge@bst.ai>
Best regards,
Krzysztof
prev parent reply other threads:[~2025-08-12 13:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:31 [PATCH v3 0/8] Introduce Black Sesame Technologies C1200 SoC and CDCU1.0 board Albert Yang
2025-08-12 12:31 ` [PATCH v3 1/8] dt-bindings: vendor-prefixes: Add Black Sesame Technologies Co., Ltd Albert Yang
2025-08-12 13:34 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 2/8] dt-bindings: arm: add Black Sesame Technologies (bst) SoC Albert Yang
2025-08-12 13:35 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 3/8] arm64: Kconfig: add ARCH_BST for Black Sesame Technologies SoCs Albert Yang
2025-08-12 12:31 ` [PATCH v3 4/8] dt-bindings: mmc: add binding for BST DWCMSHC SDHCI controller Albert Yang
2025-08-14 8:50 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 5/8] mmc: sdhci: add Black Sesame Technologies BST C1200 controller driver Albert Yang
2025-08-18 10:48 ` Ulf Hansson
2025-08-18 12:08 ` Arnd Bergmann
2025-08-18 18:16 ` Adrian Hunter
2025-08-12 12:31 ` [PATCH v3 6/8] arm64: dts: bst: add support for Black Sesame Technologies C1200 CDCU1.0 board Albert Yang
2025-08-12 16:16 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 7/8] arm64: defconfig: enable BST platform and SDHCI controller support Albert Yang
2025-08-12 13:38 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 8/8] MAINTAINERS: add and consolidate Black Sesame Technologies (BST) ARM SoC support Albert Yang
2025-08-12 13:33 ` Krzysztof Kozlowski [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=45ec2fee-9b76-4f36-8476-000fbce775c6@kernel.org \
--to=krzk@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=bst-upstream@bstai.top \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ding.wang@bst.ai \
--cc=gordon.ge@bst.ai \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=soc@lists.linux.dev \
--cc=ulf.hansson@linaro.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