From: Leo Liang <ycliang@andestech.com>
To: Yanhong Wang <yanhong.wang@starfivetech.com>
Cc: <u-boot@lists.denx.de>, Rick Chen <rick@andestech.com>,
Joe Hershberger <joe.hershberger@ni.com>,
Ramon Fried <rfried.dev@gmail.com>, Torsten Duwe <duwe@lst.de>,
Leyfoon Tan <leyfoon.tan@starfivetech.com>,
"samin . guo" <samin.guo@starfivetech.com>,
Walker Chen <walker.chen@starfivetech.com>,
"Hal Feng" <hal.feng@starfivetech.com>
Subject: Re: [PATCH v5 05/11] doc: board: starfive: Reword the make defconfig information
Date: Wed, 12 Jul 2023 04:58:19 +0000 [thread overview]
Message-ID: <ZK4y62W5ucwic7CD@ubuntu01> (raw)
In-Reply-To: <20230615093652.23161-6-yanhong.wang@starfivetech.com>
On Thu, Jun 15, 2023 at 05:36:46PM +0800, Yanhong Wang wrote:
> The defconfig file name for StarFive VisionFive2 has been changed, and
> the documentation description has also changed.
>
> Signed-off-by: Yanhong Wang <yanhong.wang@starfivetech.com>
> ---
> doc/board/starfive/visionfive2.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
next prev parent reply other threads:[~2023-07-12 4:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 9:36 [PATCH v5 00/11] Add ethernet driver for StarFive JH7110 SoC Yanhong Wang
2023-06-15 9:36 ` [PATCH v5 01/11] net: phy: Add driver for Motorcomm yt8531 gigabit ethernet phy Yanhong Wang
2023-06-15 9:36 ` [PATCH v5 02/11] net: dwc_eth_qos: Add StarFive ethernet driver glue layer Yanhong Wang
2023-06-15 9:36 ` [PATCH v5 03/11] riscv: dts: jh7110: Add ethernet device tree nodes Yanhong Wang
2023-07-12 4:56 ` Leo Liang
2023-06-15 9:36 ` [PATCH v5 04/11] riscv: dts: jh7110: Combine the board device tree files of 1.2A and 1.3B Yanhong Wang
2023-07-12 4:57 ` Leo Liang
2023-06-15 9:36 ` [PATCH v5 05/11] doc: board: starfive: Reword the make defconfig information Yanhong Wang
2023-07-12 4:58 ` Leo Liang [this message]
2023-06-15 9:36 ` [PATCH v5 06/11] configs: starfive: Enable ethernet configuration for StarFive VisionFive2 Yanhong Wang
2023-07-12 4:58 ` Leo Liang
2023-06-15 9:36 ` [PATCH v5 07/11] eeprom: starfive: Enable ID EEPROM configuration Yanhong Wang
2023-07-12 5:00 ` Leo Liang
2023-06-15 9:36 ` [PATCH v5 08/11] riscv: dts: starfive: Add support eeprom device tree node Yanhong Wang
2023-07-12 5:01 ` Leo Liang
2023-06-15 9:36 ` [PATCH v5 09/11] configs: starfive: Enable ID EEPROM configuration Yanhong Wang
2023-07-12 5:10 ` Leo Liang
2023-06-15 9:36 ` [PATCH v5 10/11] ram: starfive: Read memory size information from EEPROM Yanhong Wang
[not found] ` <SEZPR03MB806414915E2E1FACA920FC67C15DA@SEZPR03MB8064.apcprd03.prod.outlook.com>
2023-06-21 2:11 ` Rick Chen
2023-07-12 5:11 ` Leo Liang
2023-10-10 12:23 ` Andreas Schwab
2023-10-11 2:54 ` Heinrich Schuchardt
2023-10-11 4:43 ` Heinrich Schuchardt
2023-06-15 9:36 ` [PATCH v5 11/11] board: starfive: Dynamic configuration of DT for 1.2A and 1.3B Yanhong Wang
[not found] ` <SEZPR03MB8064769BE8102EB4844DDF2AC15DA@SEZPR03MB8064.apcprd03.prod.outlook.com>
2023-06-21 1:40 ` Rick Chen
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=ZK4y62W5ucwic7CD@ubuntu01 \
--to=ycliang@andestech.com \
--cc=duwe@lst.de \
--cc=hal.feng@starfivetech.com \
--cc=joe.hershberger@ni.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=rfried.dev@gmail.com \
--cc=rick@andestech.com \
--cc=samin.guo@starfivetech.com \
--cc=u-boot@lists.denx.de \
--cc=walker.chen@starfivetech.com \
--cc=yanhong.wang@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 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.