From: Heiko Stuebner <heiko@sntech.de>
To: i@chainsx.cn, Hsun Lai <i@chainsx.cn>
Cc: andrew@lunn.ch, conor+dt@kernel.org, devicetree@vger.kernel.org,
inindev@gmail.com, jonas@kwiboo.se, krzk+dt@kernel.org,
krzysztof.kozlowski@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
quentin.schulz@cherry.de, robh@kernel.org, sfr@canb.auug.org.au
Subject: Re: [v5,0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC
Date: Mon, 09 Jun 2025 11:06:10 +0200 [thread overview]
Message-ID: <2607600.Icojqenx9y@phil> (raw)
In-Reply-To: <20250602153500.1831349-1-i@chainsx.cn>
Am Montag, 2. Juni 2025, 17:35:00 Mitteleuropäische Sommerzeit schrieb Hsun Lai:
> > I tried to replicate on top of master
> > (24de2b9da3e28df323c1e096538ae1e035751adf) but couldn't, so I guess we
> > can simply ignore this warning?
>
> Yes, the same situation occurs here,
> and it has already been answered by Heiko Stübner(#2):
> https://patchwork.kernel.org/project/linux-rockchip/cover/20250516012402.580468-1-i@chainsx.cn/
Now with 6.16-rc1 out, this should disappear.
But I'd assume that bot check might have moved the binding out of the
review queue of the dt-maintainers, so I guess you might try resending
the series on top of that, because we're missing an Review/Ack on the
binding.
Heiko
prev parent reply other threads:[~2025-06-09 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 3:10 [PATCH v5 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Hsun Lai
2025-05-30 3:10 ` [PATCH v5 1/2] dt-bindings: arm: rockchip: Add Firefly ROC-RK3588S-PC Hsun Lai
2025-05-30 3:10 ` [PATCH v5 2/2] arm64: dts: rockchip: add DTs for " Hsun Lai
2025-05-30 12:52 ` [PATCH v5 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Rob Herring (Arm)
2025-06-02 10:09 ` Quentin Schulz
2025-06-02 15:35 ` [v5,0/2] " Hsun Lai
2025-06-09 9:06 ` Heiko Stuebner [this message]
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=2607600.Icojqenx9y@phil \
--to=heiko@sntech.de \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=i@chainsx.cn \
--cc=inindev@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).