From: 李维豪 <cn.liweihao@gmail.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: robh@kernel.org, hjc@rock-chips.com, andy.yan@rock-chips.com,
krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/8] dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M
Date: Fri, 5 Sep 2025 20:26:54 +0800 [thread overview]
Message-ID: <CAPEOAkS4gPiXddXi2=RqY7oJW60ewwA54=OX_Ljf1zpAgUf+_Q@mail.gmail.com> (raw)
In-Reply-To: <2267196.NgBsaNRSFp@diego>
Hi,
Heiko Stübner <heiko@sntech.de> 于2025年9月5日周五 13:53写道:
>
> Hi,
>
> Am Freitag, 5. September 2025, 04:56:27 Mitteleuropäische Sommerzeit schrieb WeiHao Li:
> > Add a clock id for mipi dsi reference clock, mipi dsi node used it.
> >
> > Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
>
> another process-related comment :-) .
>
> (1) You already got in v1 the
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
>
> So when sending a v2, please include such received tags
> (if there are no major changes to the relevant code)
>
> This prevents people from reviewing things needlessly multiple times.
> So patch 3 would look something like:
>
> ------------
> Add a clock id for mipi dsi reference clock, mipi dsi node used it.
>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
> ------------
>
> (2) As can be seen in
> https://lore.kernel.org/linux-rockchip/175690195013.3771488.435870786224873257.b4-ty@sntech.de/
>
> I already applied the two clock patches, so in newer versions don't
> send them anymore.
Got it and thanks for your patient explain.
Yours,
Weihao
next prev parent reply other threads:[~2025-09-05 12:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 2:56 [PATCH v2 0/8] drm/rockchip: Add MIPI DSI support for RK3368 WeiHao Li
2025-09-05 2:56 ` [PATCH v2 1/8] drm/rockchip: dsi: Add " WeiHao Li
2025-09-05 2:56 ` [PATCH v2 2/8] drm/rockchip: vop: add lut_size for RK3368 vop_data WeiHao Li
2025-09-05 2:56 ` [PATCH v2 3/8] dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M WeiHao Li
2025-09-05 5:52 ` Heiko Stübner
2025-09-05 12:26 ` 李维豪 [this message]
2025-09-05 2:56 ` [PATCH v2 4/8] clk: rockchip: use clock ids for SCLK_MIPIDSI_24M on rk3368 WeiHao Li
2025-09-05 2:56 ` [PATCH v2 5/8] arm64: dts: rockchip: Add display subsystem for RK3368 WeiHao Li
2025-09-05 2:56 ` [PATCH v2 6/8] arm64: dts: rockchip: Add D-PHY " WeiHao Li
2025-09-05 2:56 ` [PATCH v2 7/8] arm64: dts: rockchip: Add DSI " WeiHao Li
2025-09-05 2:56 ` [PATCH v2 8/8] dt-bindings: display: rockchip,dw-mipi-dsi: Document RK3368 DSI WeiHao Li
2025-09-05 20:45 ` Rob Herring (Arm)
2025-10-14 12:23 ` (subset) [PATCH v2 0/8] drm/rockchip: Add MIPI DSI support for RK3368 Heiko Stuebner
2025-10-14 18:06 ` Heiko Stuebner
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='CAPEOAkS4gPiXddXi2=RqY7oJW60ewwA54=OX_Ljf1zpAgUf+_Q@mail.gmail.com' \
--to=cn.liweihao@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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 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).