From: Krzysztof Kozlowski <krzk@kernel.org>
To: Elaine Zhang <zhangqing@rock-chips.com>,
mturquette@baylibre.com, sboyd@kernel.org,
kever.yang@rock-chips.com, heiko@sntech.de
Cc: linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, huangtao@rock-chips.com
Subject: Re: [PATCH v3 3/4] dt-bindings: clock: rk3588: export PCLK_VO1GRF clk id
Date: Thu, 3 Aug 2023 13:19:19 +0200 [thread overview]
Message-ID: <38b2779b-4cb8-3caf-f980-aa656277a7de@kernel.org> (raw)
In-Reply-To: <20230802072038.29996-4-zhangqing@rock-chips.com>
On 02/08/2023 09:20, Elaine Zhang wrote:
> add PCLK_VO1GRF clk id.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
v3 and still no improvements:
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
You missed at least DT list (maybe more), so this won't be tested by
automated tooling. Performing review on untested code might be a waste
of time, thus I will skip this patch entirely till you follow the
process allowing the patch to be tested.
Please kindly resend and include all necessary To/Cc entries.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-03 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 7:20 [PATCH v3 0/4] rockchip: add GATE_LINK Elaine Zhang
2023-08-02 7:20 ` [PATCH v3 1/4] clk: gate: export clk_gate_endisable Elaine Zhang
2023-08-02 7:20 ` [PATCH v3 2/4] clk: rockchip: add support for gate link Elaine Zhang
2023-08-02 7:20 ` [PATCH v3 3/4] dt-bindings: clock: rk3588: export PCLK_VO1GRF clk id Elaine Zhang
2023-08-03 11:19 ` Krzysztof Kozlowski [this message]
2023-08-02 7:20 ` [PATCH v3 4/4] clk: rockchip: rk3588: Adjust the GATE_LINK parameter Elaine Zhang
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=38b2779b-4cb8-3caf-f980-aa656277a7de@kernel.org \
--to=krzk@kernel.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=zhangqing@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®