From: "Min Lin" <linmin@eswincomputing.com>
To: gaohan@iscas.ac.cn
Cc: "Pinkesh Vaghela" <pinkesh.vaghela@einfochips.com>,
"Pritesh Patel" <pritesh.patel@einfochips.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Han Gao" <rabenda.cn@gmail.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: riscv: eswin: Add Milk-V Megrez
Date: Thu, 19 Nov 2026 09:51:32 +0800 (GMT+08:00) [thread overview]
Message-ID: <9caa3e8.a5c.1a1f1807f9c.Coremail.linmin@eswincomputing.com> (raw)
In-Reply-To: <20261118-eic7700-megrez-v2-1-0113ebc5b670@iscas.ac.cn>
> -----Original Messages-----
> From: "Han Gao via B4 Relay" <devnull+gaohan.iscas.ac.cn@kernel.org>
> Send time:Wednesday, 18/11/2026 04:00:05
> To: "Min Lin" <linmin@eswincomputing.com>, "Pinkesh Vaghela" <pinkesh.vaghela@einfochips.com>, "Pritesh Patel" <pritesh.patel@einfochips.com>, "Rob Herring" <robh@kernel.org>, "Krzysztof Kozlowski" <krzk+dt@kernel.org>, "Conor Dooley" <conor+dt@kernel.org>, "Paul Walmsley" <pjw@kernel.org>, "Palmer Dabbelt" <palmer@dabbelt.com>, "Albert Ou" <aou@eecs.berkeley.edu>, "Alexandre Ghiti" <alex@ghiti.fr>
> Cc: "Han Gao" <rabenda.cn@gmail.com>, devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, "Han Gao" <gaohan@iscas.ac.cn>
> Subject: [PATCH v2 1/2] dt-bindings: riscv: eswin: Add Milk-V Megrez
>
> From: Han Gao <gaohan@iscas.ac.cn>
>
> Add the compatible for the Milk-V Megrez, a Mini-ITX board based on the
> ESWIN EIC7700X SoC.
>
> Signed-off-by: Han Gao <gaohan@iscas.ac.cn>
> ---
> Documentation/devicetree/bindings/riscv/eswin.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/riscv/eswin.yaml b/Documentation/devicetree/bindings/riscv/eswin.yaml
> index c603c45eef2252e760818e830e9dccdf0fdae6cf..f730f5ff91797d4c2f0610f9024a74611ffeae63 100644
> --- a/Documentation/devicetree/bindings/riscv/eswin.yaml
> +++ b/Documentation/devicetree/bindings/riscv/eswin.yaml
> @@ -21,6 +21,7 @@ properties:
> oneOf:
> - items:
> - enum:
> + - milkv,megrez
> - sifive,hifive-premier-p550
> - const: eswin,eic7700
>
>
> --
> 2.47.3
>
Acked-by: Min Lin <linmin@eswincomputing.com>
Best regards,
Min Lin
next prev parent reply other threads:[~2026-11-19 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 20:00 [PATCH v2 0/2] riscv: eswin: Add Milk-V Megrez board support Han Gao via B4 Relay
2026-11-17 20:00 ` [PATCH v2 1/2] dt-bindings: riscv: eswin: Add Milk-V Megrez Han Gao via B4 Relay
2026-11-19 1:51 ` Min Lin [this message]
2026-11-17 20:00 ` [PATCH v2 2/2] riscv: dts: eswin: Add Milk-V Megrez board Han Gao via B4 Relay
2026-11-19 1:52 ` Min Lin
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=9caa3e8.a5c.1a1f1807f9c.Coremail.linmin@eswincomputing.com \
--to=linmin@eswincomputing.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gaohan@iscas.ac.cn \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pinkesh.vaghela@einfochips.com \
--cc=pjw@kernel.org \
--cc=pritesh.patel@einfochips.com \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
/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