From: "Liang He" <windhl@126.com>
To: "Martin Blumenstingl" <martin.blumenstingl@googlemail.com>
Cc: "Neil Armstrong" <narmstrong@baylibre.com>,
jbrunet@baylibre.com, mturquette@baylibre.com, sboyd@kernel.org,
khilman@baylibre.com, linux-amlogic@lists.infradead.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re:Re: [PATCH] clk/meson: Hold reference returned by of_get_parent()
Date: Mon, 27 Jun 2022 07:42:24 +0800 (CST) [thread overview]
Message-ID: <18de8077.1a5.181a2651e88.Coremail.windhl@126.com> (raw)
In-Reply-To: <CAFBinCB3=JWs78oC1GrZ_JkW56np1CAVkW25uST5hhYfoXxu-A@mail.gmail.com>
At 2022-06-27 06:02:45, "Martin Blumenstingl" <martin.blumenstingl@googlemail.com> wrote:
>Hello,
>
>thank you for submitting this patch!
>
>On Fri, Jun 24, 2022 at 12:28 PM Liang He <windhl@126.com> wrote:
>[...]
>> these bugs are compiled tested in 5.19rc2 with at91_dt_defconfig
>Please note that you're changing some drivers which are only in the
>arch/arm/configs/multi_v7_defconfig while others are only in
>arch/arm64/configs/defconfig
>I think at91_dt_defconfig will not compile any of the drivers below
>
Hi, Martin.
To simplify the building test, I use the at91_dt_defconfig to build .config
for these similar bugs in clk-at91, clk-sprd,etc.
Then I use following command to complete different compile tests for clk-meson:
make CONFIG_ARCH_MESON=y CONFIG_COMMON_CLK_MESON8B=y CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm ./drivers/clk/meson/meson8b.o
make CONFIG_ARCH_MESON=y CONFIG_COMMON_CLK_MESON_EE_CLKC=y CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm ./drivers/clk/meson/meson-eeclk.o
make CONFIG_ARCH_MESON=y CONFIG_COMMON_CLK_MESON_AO_CLKC=y CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm ./drivers/clk/meson/meson-aoclk.o
I will add these detailed compile commands in my version-2 patch and also in future patch commit.
>[...]
>> diff --git a/drivers/clk/meson/meson8b.c b/drivers/clk/meson/meson8b.c
>> index 8f3b7a94a667..54188319f349 100644
>> --- a/drivers/clk/meson/meson8b.c
>> +++ b/drivers/clk/meson/meson8b.c
>> @@ -3796,8 +3796,11 @@ static void __init meson8b_clkc_init_common(struct device_node *np,
>> struct clk *notifier_clk;
>> struct regmap *map;
>> int i, ret;
>> + struct device_node *tp;
>This function uses reverse christmas tree sorting, so the longest line
>goes on top while the shortest should stay on the bottom.
>Can you please explain what "tp" stands for? Personally I would call
>this variable parent_np, but maybe "tp" has a similar meaning.
>
>
>Best regards,
>Martin
Thanks very much, Martin.
I will send version-2 patch to keep the reverse christmas tree.
And I will follow this rule in my future patch code.
I just want to ues 'tp' as 'tmp_pointer', but your advice is
more reasonable and I will change that in version-2 patch.
Liang
prev parent reply other threads:[~2022-06-26 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 10:27 [PATCH] clk/meson: Hold reference returned by of_get_parent() Liang He
2022-06-26 22:02 ` Martin Blumenstingl
2022-06-26 23:42 ` Liang He [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=18de8077.1a5.181a2651e88.Coremail.windhl@126.com \
--to=windhl@126.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sboyd@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