From: Krzysztof Kozlowski <krzk@kernel•org>
To: Albert Yang <yangzh0906@thundersoft•com>, arnd@arndb•de
Cc: bst-upstream@bstai•top, catalin.marinas@arm•com,
conor+dt@kernel•org, devicetree@vger•kernel.org,
gordon.ge@bst•ai, krzk+dt@kernel•org,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, robh@kernel•org, will@kernel•org
Subject: Re: [PATCH v8 0/2] arm64: dts/defconfig: enable BST C1200 eMMC
Date: Tue, 2 Jun 2026 14:00:54 +0200 [thread overview]
Message-ID: <c6e0a027-38c3-4054-b971-033f021dcff4@kernel.org> (raw)
In-Reply-To: <20260602084302.2101364-1-yangzh0906@thundersoft.com>
On 02/06/2026 10:43, Albert Yang wrote:
> Hi Arnd,
>
> 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.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-02 12:01 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 [this message]
2026-06-02 12:22 ` Arnd Bergmann
-- 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=c6e0a027-38c3-4054-b971-033f021dcff4@kernel.org \
--to=krzk@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=bst-upstream@bstai$(echo .)top \
--cc=catalin.marinas@arm$(echo .)com \
--cc=conor+dt@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=gordon.ge@bst$(echo .)ai \
--cc=krzk+dt@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
--cc=will@kernel$(echo .)org \
--cc=yangzh0906@thundersoft$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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