From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Bjorn Andersson <andersson@kernel.org>,
linux-remoteproc@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 1/3] remoteproc: k3-dsp: Suppress duplicate error message in .remove()
Date: Thu, 30 Nov 2023 09:36:47 -0700 [thread overview]
Message-ID: <ZWi6HxFGOHXUE3db@p14s> (raw)
In-Reply-To: <20231129225010.ul2xcjjm7jcymmoq@pengutronix.de>
On Wed, Nov 29, 2023 at 11:50:10PM +0100, Uwe Kleine-König wrote:
> Helo Mathieu,
>
> On Wed, Nov 29, 2023 at 10:35:32AM -0700, Mathieu Poirier wrote:
> > On Thu, Nov 23, 2023 at 10:16:59PM +0100, Uwe Kleine-König wrote:
> > > diff --git a/drivers/remoteproc/ti_k3_dsp_remoteproc.c b/drivers/remoteproc/ti_k3_dsp_remoteproc.c
> > > index ef8415a7cd54..40a5fd8763fa 100644
> > > --- a/drivers/remoteproc/ti_k3_dsp_remoteproc.c
> > > +++ b/drivers/remoteproc/ti_k3_dsp_remoteproc.c
> > > @@ -835,8 +835,9 @@ static int k3_dsp_rproc_remove(struct platform_device *pdev)
> > > if (rproc->state == RPROC_ATTACHED) {
> > > ret = rproc_detach(rproc);
> > > if (ret) {
> > > + /* Note this error path leaks resources */
> >
> > I'm not sure why this comment has been added...
>
> The comment was added because there is a real problem and I didn't try
> to fix it as doing that without the hardware is hard.
>
I've looked at this again and as it turns out, you are correct on both front. I
will apply your patches as-is and ask people at TI to look at this code again.
Thanks,
Mathieu
> > > dev_err(dev, "failed to detach proc, ret = %d\n", ret);
> >
> > And why this isn't refactored in the next patch.
>
> the next patch has:
>
> - dev_err(dev, "failed to detach proc, ret = %d\n", ret);
> + dev_err(dev, "failed to detach proc (%pe)\n", ERR_PTR(ret));
>
> so this is refactored?!
>
> > > - return ret;
> > > + return 0;
> >
> > Appart from the above I'm good with this patchset.
>
> Best regards
> Uwe
>
> --
> Pengutronix e.K. | Uwe Kleine-König |
> Industrial Linux Solutions | https://www.pengutronix.de/ |
next prev parent reply other threads:[~2023-11-30 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 21:16 [PATCH 0/3] remoteproc: k3-dsp: Some cleanups Uwe Kleine-König
2023-11-23 21:16 ` [PATCH 1/3] remoteproc: k3-dsp: Suppress duplicate error message in .remove() Uwe Kleine-König
2023-11-29 17:35 ` Mathieu Poirier
2023-11-29 22:50 ` Uwe Kleine-König
2023-11-30 16:36 ` Mathieu Poirier [this message]
2023-11-30 17:19 ` Mathieu Poirier
2023-12-01 8:39 ` Uwe Kleine-König
2023-12-04 18:53 ` Hari Nagalla
2023-11-23 21:17 ` [PATCH 2/3] remoteproc: k3-dsp: Use symbolic error codes in error messages Uwe Kleine-König
2023-11-23 21:17 ` [PATCH 3/3] remoteproc: k3-dsp: Convert to platform remove callback returning void Uwe Kleine-König
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=ZWi6HxFGOHXUE3db@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-remoteproc@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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.