From: "Heiko Stübner" <heiko@sntech.de>
To: robh@kernel.org, chainsx@foxmail.com
Cc: chainsx@foxmail.com, conor+dt@kernel.org, krzk+dt@kernel.org,
sfr@canb.auug.org.au, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v1 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC
Date: Mon, 12 May 2025 15:31:16 +0200 [thread overview]
Message-ID: <3612514.V25eIC5XRa@diego> (raw)
In-Reply-To: <tencent_D5C17F39C684CD6491505763B23BACCE5106@qq.com>
Hi,
Am Montag, 12. Mai 2025, 15:20:48 Mitteleuropäische Sommerzeit schrieb chainsx@foxmail.com:
> From: Hsun Lai <chainsx@foxmail.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
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: robh@kernel.org, chainsx@foxmail.com
Cc: chainsx@foxmail.com, conor+dt@kernel.org, krzk+dt@kernel.org,
sfr@canb.auug.org.au, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v1 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC
Date: Mon, 12 May 2025 15:31:16 +0200 [thread overview]
Message-ID: <3612514.V25eIC5XRa@diego> (raw)
In-Reply-To: <tencent_D5C17F39C684CD6491505763B23BACCE5106@qq.com>
Hi,
Am Montag, 12. Mai 2025, 15:20:48 Mitteleuropäische Sommerzeit schrieb chainsx@foxmail.com:
> From: Hsun Lai <chainsx@foxmail.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
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-05-12 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:20 [PATCH v1 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC chainsx
2025-05-12 13:20 ` chainsx
2025-05-12 13:31 ` Heiko Stübner [this message]
2025-05-12 13:31 ` Heiko Stübner
-- strict thread matches above, loose matches on Subject: below --
2025-05-12 12:03 chainsx
2025-05-12 12:03 ` chainsx
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=3612514.V25eIC5XRa@diego \
--to=heiko@sntech.de \
--cc=chainsx@foxmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.