public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Yang <yangzh0906@thundersoft.com>
To: arnd@arndb.de
Cc: soc@lists.linux.dev, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
	will@kernel.org, krzk@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, ulf.hansson@linaro.org, conor+dt@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:52:53 +0800	[thread overview]
Message-ID: <20251031045253.789621-1-yangzh0906@thundersoft.com> (raw)
In-Reply-To: <20251016120558.2390960-1-yangzh0906@thundersoft.com>

Hi Arnd,

Following up on the v5 series for BST C1200 SoC support. The dt-bindings
patches have received the necessary reviews (Rob's Acked-by for 1/6 and
Krzysztof's Reviewed-by for 2/6).

I now understand that the SoC-specific patches (Kconfig, DTS, defconfig,
MAINTAINERS) should be reviewed by the ARM SoC maintainers rather than
the DT bindings reviewers. Please correct me if I'm misunderstanding the
process.

In your previous feedback [1], you mentioned you'd be happy to merge the
SoC portions in arch/arm64 and suggested resubmitting for 6.19 once
6.18-rc1 is out. Could you advise on the next steps? Is there anything
I should prepare or address before the 6.19 merge window?

If I've misunderstood anything about the process, please let me know.

Series: https://lore.kernel.org/lkml/20251016120558.2390960-1-yangzh0906@thundersoft.com/

[1] https://lore.kernel.org/lkml/09b1318e-21dc-4354-8733-866b70696295@app.fastmail.com/

Thanks,
Albert


  parent reply	other threads:[~2025-10-31  7:15 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
2025-10-31  4:52 ` Albert Yang [this message]
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=20251031045253.789621-1-yangzh0906@thundersoft.com \
    --to=yangzh0906@thundersoft.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=soc@lists.linux.dev \
    --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