From: patchwork-bot+linux-riscv@kernel.org
To: Jinyu Tang <tangjinyu@tinylab.org>
Cc: linux-riscv@lists.infradead.org, william.qiu@starfivetech.com,
hal.feng@starfivetech.com, conor.dooley@microchip.com,
palmer@dabbelt.com, apatel@ventanamicro.com,
ttjjyystupid@163.com, falcon@tinylab.org, wangjiexun@tinylab.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: defconfig : add CONFIG_MMC_DW for starfive
Date: Mon, 06 Nov 2023 15:00:29 +0000 [thread overview]
Message-ID: <169928282907.16503.712664664958063675.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230912133128.5247-1-tangjinyu@tinylab.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 12 Sep 2023 21:31:28 +0800 you wrote:
> If these config not set, mmc can't run for jh7110, rootfs can't
> be found when using SD card. So set CONFIG_MMC_DW=y like arm64
> defconfig, and set CONFIG_MMC_DW_STARFIVE=y for starfive. Then
> starfive vf2 board can start SD card rootfs with mainline defconfig
> and dtb.
>
> Signed-off-by: Jinyu Tang <tangjinyu@tinylab.org>
>
> [...]
Here is the summary with links:
- [v2] riscv: defconfig : add CONFIG_MMC_DW for starfive
https://git.kernel.org/riscv/c/07863871dfb1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-06 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 13:31 [PATCH v2] riscv: defconfig : add CONFIG_MMC_DW for starfive Jinyu Tang
2023-09-12 16:23 ` Conor Dooley
2023-11-06 15:00 ` patchwork-bot+linux-riscv [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=169928282907.16503.712664664958063675.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=apatel@ventanamicro.com \
--cc=conor.dooley@microchip.com \
--cc=falcon@tinylab.org \
--cc=hal.feng@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=tangjinyu@tinylab.org \
--cc=ttjjyystupid@163.com \
--cc=wangjiexun@tinylab.org \
--cc=william.qiu@starfivetech.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