From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Li Jun <lijun01@kylinos.cn>
Cc: andersson@kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] remoteproc: Cancel init error to zero
Date: Fri, 6 Jun 2025 08:42:26 -0600 [thread overview]
Message-ID: <aEL-Ug8w9KuG8rc4@p14s> (raw)
In-Reply-To: <20250604094802.127472-1-lijun01@kylinos.cn>
Good day,
On Wed, Jun 04, 2025 at 05:48:02PM +0800, Li Jun wrote:
> The init action consume additional CPU cycles. the
I'm fine with code cleanup but call it what it is rather than trying to justify
it with dubious claims. Please remove the above sentence.
> reset_control_assert(wkupm3->rsts) should assign a value
> to 'error' before it is return.so the var don't need init
Proper punctuation after a period.
Thanks,
Mathieu
> to 0.
>
> Signed-off-by: Li Jun <lijun01@kylinos.cn>
> ---
> drivers/remoteproc/wkup_m3_rproc.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/remoteproc/wkup_m3_rproc.c b/drivers/remoteproc/wkup_m3_rproc.c
> index d8be21e71721..24d72fcc26f9 100644
> --- a/drivers/remoteproc/wkup_m3_rproc.c
> +++ b/drivers/remoteproc/wkup_m3_rproc.c
> @@ -77,9 +77,7 @@ static int wkup_m3_rproc_stop(struct rproc *rproc)
> struct platform_device *pdev = wkupm3->pdev;
> struct device *dev = &pdev->dev;
> struct wkup_m3_platform_data *pdata = dev_get_platdata(dev);
> - int error = 0;
> -
> - error = reset_control_assert(wkupm3->rsts);
> + int error = reset_control_assert(wkupm3->rsts);
>
> if (!wkupm3->rsts && pdata->assert_reset(pdev, pdata->reset_name)) {
> dev_err(dev, "Unable to assert reset of wkup_m3!\n");
> --
> 2.25.1
>
>
prev parent reply other threads:[~2025-06-06 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 9:48 [PATCH] remoteproc: Cancel init error to zero Li Jun
2025-06-06 14:42 ` Mathieu Poirier [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=aEL-Ug8w9KuG8rc4@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=lijun01@kylinos.cn \
--cc=linux-remoteproc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.