From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Gui-Dong Han <hanguidong02@gmail.com>,
Joshua Milas <josh.milas@gmail.com>
Cc: michael.opdenacker@rootcommit.com, tglx@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
pjw@kernel.org, samuel.holland@sifive.com,
unicorn_wang@outlook.com, inochiama@gmail.com,
daniel.lezcano@linaro.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
liujingqi@lanxincomputing.com, alexander.sverdlin@gmail.com,
rabenda.cn@gmail.com, dlan@kernel.org, chao.wei@sophgo.com,
anup@brainfault.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
sophgo@lists.linux.dev, Wang Jiayue <akaieurus@gmail.com>,
Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v5 5/5] riscv64: dts: sophgo: add initial Milk-V Duo S board support
Date: Wed, 20 May 2026 22:46:14 +0200 [thread overview]
Message-ID: <5354f909-438b-4994-808c-6d055c58c901@rootcommit.com> (raw)
In-Reply-To: <CALbr=LYJKJREwh8KMqsgcXwd+jx0W7gFFFuBk-izNdgzkQU6Pg@mail.gmail.com>
Joshua, Gui-Dong
(my apologies for my previous-email with HTML content... bad default
Thunderbird settings!
On 4/21/26 6:13 PM, Gui-Dong Han wrote:
> On Fri, Apr 3, 2026 at 7:16 PM Joshua Milas <josh.milas@gmail.com> wrote:
>> This adds initial riscv support for the Milk-V Duo S board
>> [1] making it possible to boot Linux to the command line.
>>
>> Link: https://milkv.io/duo-s [1]
>>
>> Signed-off-by: Joshua Milas <josh.milas@gmail.com>
> Great work, thanks Joshua! I really like this board.
>
> I encountered the same issue Michael Opdenacker saw in v4, but
> enabling the MDIO-related configs resolved it.
>
> I'll keep using and testing this series and provide further feedback
> if anything comes up. Next, I plan to test the arm64 side and will
> also try developing an efuse driver.
>
> Tested-by: Gui-Dong Han <hanguidong02@gmail.com>
> Reviewed-by: Gui-Dong Han <hanguidong02@gmail.com>
What about submitting a new iteration of your patchset? I guess the last
one was too close to the merge window to make it, but if you submit a
new version not too late and review it quickly enough, we could make it
this time.
Don't hesitate to let us know if you need help (happy to post the new
iteration if you don't have time).
Thanks in advance
Cheers
Michael.
--
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com
prev parent reply other threads:[~2026-05-20 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 11:15 [PATCH v5 0/5] Add initial Milk-V Duo S board support Joshua Milas
2026-04-03 11:15 ` [PATCH v5 1/5] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2026-04-04 8:05 ` Krzysztof Kozlowski
2026-04-03 11:15 ` [PATCH v5 2/5] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2026-04-03 11:15 ` [PATCH v5 3/5] dt-bindings: soc: sophgo: add sg2000 plic and clint documentation Joshua Milas
2026-04-04 8:10 ` Krzysztof Kozlowski
2026-04-03 11:15 ` [PATCH v5 4/5] riscv64: dts: sophgo: add SG2000 dtsi Joshua Milas
2026-04-21 16:11 ` Gui-Dong Han
2026-04-03 11:15 ` [PATCH v5 5/5] riscv64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2026-04-21 16:13 ` Gui-Dong Han
2026-05-20 20:46 ` Michael Opdenacker [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=5354f909-438b-4994-808c-6d055c58c901@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=akaieurus@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexander.sverdlin@gmail.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=hanguidong02@gmail.com \
--cc=inochiama@gmail.com \
--cc=josh.milas@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liujingqi@lanxincomputing.com \
--cc=me@ziyao.cc \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=sophgo@lists.linux.dev \
--cc=tglx@kernel.org \
--cc=unicorn_wang@outlook.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