From: Jerome Brunet <jbrunet@baylibre.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
neil.armstrong@linaro.org
Cc: mturquette@baylibre.com, sboyd@kernel.org, khilman@baylibre.com,
martin.blumenstingl@googlemail.com,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] clk: meson: pll: remove unneeded semicolon
Date: Wed, 14 Jun 2023 16:05:30 +0200 [thread overview]
Message-ID: <1jr0qef893.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20230614084808.98819-1-jiapeng.chong@linux.alibaba.com>
On Wed 14 Jun 2023 at 16:48, Jiapeng Chong <jiapeng.chong@linux.alibaba.com> wrote:
> No functional modification involved.
>
> ./drivers/clk/meson/clk-pll.c:373:2-3: Unneeded semicolon.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=5533
Not sure this tag is relevant
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Apart from this
Reviewed-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> drivers/clk/meson/clk-pll.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/meson/clk-pll.c b/drivers/clk/meson/clk-pll.c
> index 56ec2210f1ad..8fef90bf962f 100644
> --- a/drivers/clk/meson/clk-pll.c
> +++ b/drivers/clk/meson/clk-pll.c
> @@ -370,7 +370,7 @@ static int meson_clk_pll_enable(struct clk_hw *hw)
> usleep_range(10, 20);
> meson_parm_write(clk->map, &pll->current_en, 1);
> usleep_range(40, 50);
> - };
> + }
>
> if (MESON_PARM_APPLICABLE(&pll->l_detect)) {
> meson_parm_write(clk->map, &pll->l_detect, 1);
next prev parent reply other threads:[~2023-06-14 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 8:48 [PATCH] clk: meson: pll: remove unneeded semicolon Jiapeng Chong
2023-06-14 14:05 ` Jerome Brunet [this message]
2023-06-14 20:09 ` Martin Blumenstingl
2023-06-15 10:36 ` Jerome Brunet
2023-06-22 18:59 ` Dmitry Rokosov
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=1jr0qef893.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=abaci@linux.alibaba.com \
--cc=jiapeng.chong@linux.alibaba.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=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--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