From: "Arnd Bergmann" <arnd@arndb.de>
To: "gordon.ge" <gordon.ge@bst.ai>, soc@lists.linux.dev
Cc: "yangzh0906@thundersoft.com" <yangzh0906@thundersoft.com>,
linux-arm-kernel@lists.infradead.org,
bst-upstream <bst-upstream@bstai.top>
Subject: Re: [GIT PULL] arm64: BST C1200 eMMC DTS + defconfig for v7.2
Date: Tue, 09 Jun 2026 15:24:54 +0200 [thread overview]
Message-ID: <731e235f-96c0-4233-b316-c7887fb99bf9@app.fastmail.com> (raw)
In-Reply-To: <20260603.193147-gordon.ge@bst.ai>
On Wed, Jun 3, 2026, at 13:31, gordon.ge@bst.ai wrote:
> The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
> arm64: BST C1200 eMMC DTS + defconfig for v7.2
>
> Black Sesame Technologies:
>
> Enable eMMC controller on BST C1200 CDCU1.0 board:
> - Add mmc0 node in bstc1200.dtsi (DWCMSHC SDHCI controller)
> - Add fixed clock definition and reserved SRAM bounce buffer
> - Enable mmc0 with 8-bit bus on CDCU1.0 ADAS 4C2G board
> - Enable CONFIG_MMC_SDHCI_BST=y in arm64 defconfig
>
> The MMC driver was merged via mmc-next in v7.1-rc1.
> These are the remaining DTS and defconfig pieces.
Hi Gordon,
There are two more formal mistakes here in your
pull request, please fix:
- keep the defconfig patch separate from the devicetree changes,
as we will merge them separately.
- on each patch, make sure there is at least a 'Signed-off-by'
tag from the committer (plus author, if different), and
ideally any 'Reviewed-by', 'Acked-by' or 'Tested-by' tags
you have received.
Arnd
prev parent reply other threads:[~2026-06-09 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 11:31 [GIT PULL] arm64: BST C1200 eMMC DTS + defconfig for v7.2 gordon.ge
2026-06-09 13:24 ` Arnd Bergmann [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=731e235f-96c0-4233-b316-c7887fb99bf9@app.fastmail.com \
--to=arnd@arndb.de \
--cc=bst-upstream@bstai.top \
--cc=gordon.ge@bst.ai \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@lists.linux.dev \
--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