From: E Shattow <e@freeshell.de>
To: Hal Feng <hal.feng@starfivetech.com>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Tom Rini <trini@konsulko.com>, Rick Chen <rick@andestech.com>,
Sumit Garg <sumit.garg@kernel.org>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v1 0/2] Add support for StarFive VisionFive 2 Lite eMMC board
Date: Thu, 2 Apr 2026 03:52:28 -0700 [thread overview]
Message-ID: <617dfafa-bb37-4ce0-80c9-6e4334f488cc@freeshell.de> (raw)
In-Reply-To: <20260402070041.2418-1-hal.feng@starfivetech.com>
Hi Hal,
On 4/2/26 00:00, Hal Feng wrote:
> VisionFive 2 Lite eMMC board uses the eMMC as storage component instead
> of the MicroSD card in VisionFive 2 Lite board. The device tree of
> VisionFive 2 Lite eMMC board is already upstream in Linux, so add support
> in u-boot also.
>
> Hal Feng (2):
> configs: visionfive2: Add VisionFive 2 Lite eMMC DT to OF_LIST
> board: starfive: visionfive2: Support VisionFive 2 Lite eMMC
>
> board/starfive/visionfive2/spl.c | 7 ++++++-
> board/starfive/visionfive2/starfive_visionfive2.c | 6 +++++-
> configs/starfive_visionfive2_defconfig | 2 +-
> 3 files changed, 12 insertions(+), 3 deletions(-)
>
>
> base-commit: 98cf83d81617f489d7ff7bf78d33e693e2799254
Looks good to me (for -next). For the series:
Reviewed-by: E Shattow <e@freeshell.de>
prev parent reply other threads:[~2026-04-02 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 7:00 [PATCH v1 0/2] Add support for StarFive VisionFive 2 Lite eMMC board Hal Feng
2026-04-02 7:00 ` [PATCH v1 1/2] configs: visionfive2: Add VisionFive 2 Lite eMMC DT to OF_LIST Hal Feng
2026-04-02 7:00 ` [PATCH v1 2/2] board: starfive: visionfive2: Support VisionFive 2 Lite eMMC Hal Feng
2026-04-02 7:10 ` [PATCH v1 0/2] Add support for StarFive VisionFive 2 Lite eMMC board Hal Feng
2026-04-02 10:52 ` E Shattow [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=617dfafa-bb37-4ce0-80c9-6e4334f488cc@freeshell.de \
--to=e@freeshell.de \
--cc=emil.renner.berthing@canonical.com \
--cc=hal.feng@starfivetech.com \
--cc=rick@andestech.com \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=ycliang@andestech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.