From: Albert Yang <yangzh0906@thundersoft.com>
To: krzk@kernel.org, arnd@arndb.de
Cc: krzk+dt@kernel.org, robh@kernel.org, conor+dt@kernel.org,
gordon.ge@bst.ai, bst-upstream@bstai.top,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, yangzh0906@thundersoft.com
Subject: [PING] Re: [PATCH v7 0/2] arm64: dts/defconfig: enable BST C1200 eMMC
Date: Mon, 13 Apr 2026 16:34:41 +0800 [thread overview]
Message-ID: <20260413083441.1758438-1-yangzh0906@thundersoft.com> (raw)
In-Reply-To: <20260310091211.4171307-1-yangzh0906@thundersoft.com>
Hi Krzysztof, Arnd, Rob, and Conor,
Gentle ping for this v7 series posted on 2026-03-10:
https://lore.kernel.org/lkml/20260310091211.4171307-1-yangzh0906@thundersoft.com/
This series only contains the remaining DTS + defconfig parts for BST C1200 eMMC:
- 1/2 arm64: dts: bst: enable eMMC controller in C1200 CDCU1.0 board
- 2/2 arm64: defconfig: enable BST SDHCI controller
The MMC driver-side patches were already applied in mmc-next, so this series is for
arm64/DT review and merge path.
No functional code changes since v7. If preferred, I can send a rebase/refresh (v8)
on top of current mainline immediately.
Could you please help review and let me know if any changes are still needed?
Thanks for your time.
Best regards,
Albert
next prev parent reply other threads:[~2026-04-13 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 9:12 [PATCH v7 0/2] arm64: dts/defconfig: enable BST C1200 eMMC Albert Yang
2026-03-10 9:12 ` [PATCH v7 1/2] arm64: dts: bst: enable eMMC controller in C1200 CDCU1.0 board Albert Yang
2026-04-17 8:47 ` gordon.ge
2026-03-10 9:12 ` [PATCH v7 2/2] arm64: defconfig: enable BST SDHCI controller Albert Yang
2026-04-17 8:38 ` gordon.ge
2026-04-13 8:34 ` Albert Yang [this message]
2026-04-13 9:09 ` [PING] Re: [PATCH v7 0/2] arm64: dts/defconfig: enable BST C1200 eMMC Krzysztof Kozlowski
2026-04-14 3:10 ` 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=20260413083441.1758438-1-yangzh0906@thundersoft.com \
--to=yangzh0906@thundersoft.com \
--cc=arnd@arndb.de \
--cc=bst-upstream@bstai.top \
--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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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