From: patchwork-bot+linux-riscv@kernel.org
To: Han Gao <gaohan@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
jszhang@kernel.org, fustini@kernel.org, guoren@kernel.org,
wefu@redhat.com, rabenda.cn@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] riscv: dts: thead: Add Milk-V Meles support
Date: Sun, 01 Nov 2026 22:15:45 +0000 [thread overview]
Message-ID: <179357134580.2624073.9566786925548319371.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001-rv-meles-v2-0-c61052262f84@iscas.ac.cn>
Hello:
This series was applied to riscv/linux.git (fixes)
by Drew Fustini <fustini@kernel.org>:
On Thu, 01 Oct 2026 15:44:09 +0800 you wrote:
> Milk-V Meles is a single-board computer powered by T-HEAD's TH1520
> SoC with four C910 RISC-V cores. Add the board compatible and device
> tree for the Milk-V Meles.
>
> Enable UART0, eMMC, microSD, Gigabit Ethernet and the PWM fan, and
> name the GPIO lines exposed on the 40-pin header. Add AP6256 Wi-Fi
> support over SDIO and enable HDMI output through the DC8200 display
> controller and DW-HDMI transmitter.
>
> [...]
Here is the summary with links:
- [v2,1/4] dt-bindings: riscv: thead: add Milk-V Meles
https://git.kernel.org/riscv/c/2c8613ec65f4
- [v2,2/4] riscv: dts: thead: add Milk-V Meles
https://git.kernel.org/riscv/c/8360e1bcc246
- [v2,3/4] riscv: dts: thead: enable AP6256 Wi-Fi on Milk-V Meles
https://git.kernel.org/riscv/c/a7f2539005c4
- [v2,4/4] riscv: dts: thead: enable HDMI on Milk-V Meles
https://git.kernel.org/riscv/c/d43b33e0253c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Han Gao <gaohan@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
jszhang@kernel.org, fustini@kernel.org, guoren@kernel.org,
wefu@redhat.com, rabenda.cn@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] riscv: dts: thead: Add Milk-V Meles support
Date: Sun, 01 Nov 2026 22:15:45 +0000 [thread overview]
Message-ID: <179357134580.2624073.9566786925548319371.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001-rv-meles-v2-0-c61052262f84@iscas.ac.cn>
Hello:
This series was applied to riscv/linux.git (fixes)
by Drew Fustini <fustini@kernel.org>:
On Thu, 01 Oct 2026 15:44:09 +0800 you wrote:
> Milk-V Meles is a single-board computer powered by T-HEAD's TH1520
> SoC with four C910 RISC-V cores. Add the board compatible and device
> tree for the Milk-V Meles.
>
> Enable UART0, eMMC, microSD, Gigabit Ethernet and the PWM fan, and
> name the GPIO lines exposed on the 40-pin header. Add AP6256 Wi-Fi
> support over SDIO and enable HDMI output through the DC8200 display
> controller and DW-HDMI transmitter.
>
> [...]
Here is the summary with links:
- [v2,1/4] dt-bindings: riscv: thead: add Milk-V Meles
https://git.kernel.org/riscv/c/2c8613ec65f4
- [v2,2/4] riscv: dts: thead: add Milk-V Meles
https://git.kernel.org/riscv/c/8360e1bcc246
- [v2,3/4] riscv: dts: thead: enable AP6256 Wi-Fi on Milk-V Meles
https://git.kernel.org/riscv/c/a7f2539005c4
- [v2,4/4] riscv: dts: thead: enable HDMI on Milk-V Meles
https://git.kernel.org/riscv/c/d43b33e0253c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
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-01 22:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 7:44 [PATCH v2 0/4] riscv: dts: thead: Add Milk-V Meles support Han Gao
2026-10-01 7:44 ` Han Gao
2026-10-01 7:44 ` [PATCH v2 1/4] dt-bindings: riscv: thead: add Milk-V Meles Han Gao
2026-10-01 7:44 ` Han Gao
2026-10-01 19:05 ` Conor Dooley
2026-10-01 19:05 ` Conor Dooley
2026-10-01 19:34 ` Drew Fustini
2026-10-01 19:34 ` Drew Fustini
2026-10-01 7:44 ` [PATCH v2 2/4] riscv: dts: " Han Gao
2026-10-01 7:44 ` Han Gao
2026-10-07 22:03 ` Yao Zi
2026-10-07 22:03 ` Yao Zi
2026-10-30 17:03 ` Drew Fustini
2026-10-30 17:03 ` Drew Fustini
2026-10-01 7:44 ` [PATCH v2 3/4] riscv: dts: thead: enable AP6256 Wi-Fi on " Han Gao
2026-10-01 7:44 ` Han Gao
2026-10-01 7:44 ` [PATCH v2 4/4] riscv: dts: thead: enable HDMI " Han Gao
2026-10-01 7:44 ` Han Gao
2026-10-08 7:05 ` [PATCH v2 0/4] riscv: dts: thead: Add Milk-V Meles support Guo Ren
2026-10-08 7:05 ` Guo Ren
2026-10-12 23:32 ` Drew Fustini
2026-10-12 23:32 ` Drew Fustini
2026-11-01 22:15 ` patchwork-bot+linux-riscv [this message]
2026-11-01 22:15 ` patchwork-bot+linux-riscv
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=179357134580.2624073.9566786925548319371.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fustini@kernel.org \
--cc=gaohan@iscas.ac.cn \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=wefu@redhat.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.