linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Albert Yang <yangzh0906@thundersoft.com>
To: krzysztof.kozlowski@linaro.org
Cc: arnd@arndb.de, bst-upstream@bstai.top, catalin.marinas@arm.com,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	gordon.ge@bst.ai, krzk+dt@kernel.org, krzk@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, robh@kernel.org,
	ulf.hansson@linaro.org, will@kernel.org,
	yangzh0906@thundersoft.com
Subject: Re: [PATCH v5 0/6] arm64: introduce Black Sesame Technologies C1200 SoC and CDCU1.0 board
Date: Fri, 31 Oct 2025 12:38:03 +0800	[thread overview]
Message-ID: <20251031043803.781326-1-yangzh0906@thundersoft.com> (raw)
In-Reply-To: <ad1bb032-6d58-435b-b2bc-04aa26d41d58@linaro.org>

On Thu, Oct 30, 2025 at 04:04:39PM +0100, Krzysztof Kozlowski wrote:
> On 30/10/2025 12:40, Albert Yang wrote:
> > Hi Krzysztof,
> >
> > Gentle ping on this series. It's been two weeks since v5 was posted.
> >
> > This version addresses the DTS coding style and property ordering issues
> > from our previous discussion [1]. Following Arnd's suggestion [2], the MMC
> > patches have been removed and will be submitted separately.
> >
> > Patch 2/6 (arm bindings) already has your Reviewed-by. The remaining
> > patches (Kconfig, DTS, defconfig, and MAINTAINERS) are ready for review
> > when you have time.
>
> I don't understand this ping. You received the reviewed from me or other
> maintainers, where we were responsible to give such review. Probably you
> assume that my job is to review something else here, but sorry, that's
> not my job at the time of this patchset was prepared (we don't count
> here recent changes because that would mean you ping me after few days...).
>

My apologies for the confusion. You're absolutely right about the
maintainer responsibilities.

I should clarify why I pinged you: You provided valuable feedback on
earlier versions of this series, including the DTS patches. Since those
changes were made based on your input but hadn't received confirmation,
I wanted to make sure they properly addressed your concerns. However, I
now understand that the SoC-specific patches (Kconfig, DTS, defconfig,
MAINTAINERS) should be reviewed by the ARM SoC maintainers.

Thank you for your reviews and for clarifying the proper process. I'll
follow up with Arnd for the remaining patches.

Best regards,
Albert


  reply	other threads:[~2025-10-31  4:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 12:05 [PATCH v5 0/6] arm64: introduce Black Sesame Technologies C1200 SoC and CDCU1.0 board Albert Yang
2025-10-16 12:05 ` [PATCH v5 1/6] dt-bindings: vendor-prefixes: Add Black Sesame Technologies Co., Ltd Albert Yang
2025-10-16 12:05 ` [PATCH v5 2/6] dt-bindings: arm: add Black Sesame Technologies (bst) SoC Albert Yang
2025-10-16 12:05 ` [PATCH v5 3/6] arm64: Kconfig: add ARCH_BST for Black Sesame Technologies SoCs Albert Yang
2025-10-16 12:05 ` [PATCH v5 4/6] arm64: dts: bst: add support for Black Sesame Technologies C1200 CDCU1.0 board Albert Yang
2025-10-16 12:05 ` [PATCH v5 5/6] arm64: defconfig: enable BST platform support Albert Yang
2025-10-16 12:05 ` [PATCH v5 6/6] MAINTAINERS: add Black Sesame Technologies (BST) ARM SoC support Albert Yang
2025-10-30 11:40 ` [PATCH v5 0/6] arm64: introduce Black Sesame Technologies C1200 SoC and CDCU1.0 board Albert Yang
2025-10-30 15:04   ` Krzysztof Kozlowski
2025-10-31  4:38     ` Albert Yang [this message]
2025-10-31  4:52 ` Albert Yang
2025-11-18 12:07   ` Albert Yang
  -- strict thread matches above, loose matches on Subject: below --
2025-10-16 12:04 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=20251031043803.781326-1-yangzh0906@thundersoft.com \
    --to=yangzh0906@thundersoft.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=gordon.ge@bst.ai \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).