From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Li kunyu <kunyu@nfschina.com>
Cc: agross@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: the return value statement of the gcc_sm6350_probe function has an extra semicolon
Date: Mon, 27 Jun 2022 15:15:18 -0500 [thread overview]
Message-ID: <YroP1pW3dzoV9F4D@builder.lan> (raw)
In-Reply-To: <20220627020500.135125-1-kunyu@nfschina.com>
On Sun 26 Jun 21:05 CDT 2022, Li kunyu wrote:
> I think this semicolon could be deleted.
>
Thank you for the patch Li.
Please look at the git log for suggestions about the prefix for your
commit subject (clk: qcom: gcc-sm6350: in this case).
I've updated the commit message and picked up the patch.
Regards,
Bjorn
> Signed-off-by: Li kunyu <kunyu@nfschina.com>
> ---
> drivers/clk/qcom/gcc-sm6350.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/qcom/gcc-sm6350.c b/drivers/clk/qcom/gcc-sm6350.c
> index a4f7fba70393..69412400efa4 100644
> --- a/drivers/clk/qcom/gcc-sm6350.c
> +++ b/drivers/clk/qcom/gcc-sm6350.c
> @@ -2558,7 +2558,7 @@ static int gcc_sm6350_probe(struct platform_device *pdev)
> if (ret)
> return ret;
>
> - return qcom_cc_really_probe(pdev, &gcc_sm6350_desc, regmap);;
> + return qcom_cc_really_probe(pdev, &gcc_sm6350_desc, regmap);
> }
>
> static struct platform_driver gcc_sm6350_driver = {
> --
> 2.18.2
>
next prev parent reply other threads:[~2022-06-27 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 2:05 [PATCH] drivers: the return value statement of the gcc_sm6350_probe function has an extra semicolon Li kunyu
2022-06-27 20:15 ` Bjorn Andersson [this message]
2022-06-28 20:19 ` (subset) " Bjorn Andersson
2022-06-29 1:41 ` Li kunyu
2022-06-29 1:42 ` Li kunyu
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=YroP1pW3dzoV9F4D@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=kunyu@nfschina.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@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;
as well as URLs for NNTP newsgroup(s).