From: Conor Dooley <conor@kernel.org>
To: gaohan@iscas.ac.cn
Cc: 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>, Han Gao <rabenda.cn@gmail.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: eswin: Add Milk-V Megrez board
Date: Wed, 18 Nov 2026 18:06:57 +0000 [thread overview]
Message-ID: <20261118-tiny-divinity-920c0b7f3be1@spud> (raw)
In-Reply-To: <20261118-eic7700-megrez-v1-2-af8334b88336@iscas.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 52 bytes --]
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: gaohan@iscas.ac.cn
Cc: 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>, Han Gao <rabenda.cn@gmail.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: eswin: Add Milk-V Megrez board
Date: Wed, 18 Nov 2026 18:06:57 +0000 [thread overview]
Message-ID: <20261118-tiny-divinity-920c0b7f3be1@spud> (raw)
In-Reply-To: <20261118-eic7700-megrez-v1-2-af8334b88336@iscas.ac.cn>
[-- Attachment #1.1: Type: text/plain, Size: 52 bytes --]
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-11-18 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 19:55 [PATCH 0/2] riscv: eswin: Add Milk-V Megrez board support Han Gao
2026-11-17 19:55 ` Han Gao via B4 Relay
2026-11-17 19:55 ` Han Gao via B4 Relay
2026-11-17 19:55 ` [PATCH 1/2] dt-bindings: riscv: eswin: Add Milk-V Megrez Han Gao
2026-11-17 19:55 ` Han Gao via B4 Relay
2026-11-17 19:55 ` Han Gao via B4 Relay
2026-11-18 18:06 ` Conor Dooley
2026-11-18 18:06 ` Conor Dooley
2026-11-17 19:55 ` [PATCH 2/2] riscv: dts: eswin: Add Milk-V Megrez board Han Gao
2026-11-17 19:55 ` Han Gao via B4 Relay
2026-11-17 19:55 ` Han Gao via B4 Relay
2026-11-18 18:06 ` Conor Dooley [this message]
2026-11-18 18:06 ` Conor Dooley
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=20261118-tiny-divinity-920c0b7f3be1@spud \
--to=conor@kernel.org \
--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=linmin@eswincomputing.com \
--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 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.