[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3612514.V25eIC5XRa@diego>
Date: Mon, 12 May 2025 15:31:16 +0200
From: Heiko StĂĽbner <heiko@...ech.de>
To: robh@...nel.org, chainsx@...mail.com
Cc: chainsx@...mail.com, conor+dt@...nel.org, krzk+dt@...nel.org,
sfr@...b.auug.org.au, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH v1 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC
Hi,
Am Montag, 12. Mai 2025, 15:20:48 Mitteleuropäische Sommerzeit schrieb chainsx@...mail.com:
> From: Hsun Lai <chainsx@...mail.com>
>
> This series add support for Firefly Station-M3/ROC-RK3588S-PC.
>
> Info of device can be found at:
> https://wiki.t-firefly.com/en/Station-M3/index.html
>
> Changes in v1:
> - Add support for Firefly ROC-RK3588S-PC
>
> Hsun Lai (2):
> dt-bindings: arm: rockchip: Add Firefly ROC-RK3588S-PC
> arm64: dts: rockchip: add DTs for Firefly ROC-RK3588S-PC
hmm, you seem to be using git-send-email, but your mails did not
get in-reply-to headers. Normally git-send-email should detect the
cover-letter + patches thing and tie them together to a mail thread
when you send them with a "git send-email *.patch" or similar .
Heiko
Powered by blists - more mailing lists