From: Tanmay Shah <tanmay.shah@amd.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: mathieu.poirier@linaro.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, Tarak Reddy <tarak.reddy@amd.com>
Subject: Re: [PATCH v4 2/2] remoteproc: enhance rproc_put() for clusters
Date: Mon, 29 Jan 2024 11:43:06 -0600 [thread overview]
Message-ID: <ef007d96-4aa6-4e29-bbe6-3d6cb82475ba@amd.com> (raw)
In-Reply-To: <4xqmpxq4uqqxmgsf5lzxo3qjxmoeu6cpb4iqvtxefyiqlt3pzk@g76y2r4uxkiw>
On 1/26/24 11:38 AM, Bjorn Andersson wrote:
> On Wed, Jan 03, 2024 at 02:11:25PM -0800, Tanmay Shah wrote:
> > This patch enhances rproc_put() to support remoteproc clusters
> > with multiple child nodes as in rproc_get_by_phandle().
> >
> > Signed-off-by: Tarak Reddy <tarak.reddy@amd.com>
> > Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
>
> As described in the first patch, this documents that Tarak first
> certified the origin of this patch, then you certify the origin as you
> handle the patch.
>
> But according to From: you're the author, so how could Tarak have
> certified the origin before you authored the patch?
>
> Either correct the author, or add Co-developed-by, if that's what
> happened.
>
> > ---
> > drivers/remoteproc/remoteproc_core.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> > index 0b3b34085e2f..f276956f2c5c 100644
> > --- a/drivers/remoteproc/remoteproc_core.c
> > +++ b/drivers/remoteproc/remoteproc_core.c
> > @@ -2554,7 +2554,11 @@ EXPORT_SYMBOL(rproc_free);
> > */
> > void rproc_put(struct rproc *rproc)
> > {
> > - module_put(rproc->dev.parent->driver->owner);
> > + if (rproc->dev.parent->driver)
> > + module_put(rproc->dev.parent->driver->owner);
> > + else
> > + module_put(rproc->dev.parent->parent->driver->owner);
> > +
>
> This does however highlight a bug that was introduced by patch 1, please
> avoid this by squashing the two patches together (and use
> Co-developed-by as needed).
Thanks Bjorn for catching this. This change originally was developed by Tarak, but I sent upstream based on his patch so I missed
to update his name as author. I should update author name.
However, if we are going to squash this in first patch, then I think, first patch's author will stay as it is.
Following Action Item on me for v5:
1) Fix commit text in first patch.
2) Squash second patch in first.
3) Add my s-o-b signature after Mathieu's
4) Add Tarak's s-o-b as well. As he developed second patch.
Hope got it all.
Thanks,
Tanmay
>
> Regards,
> Bjorn
>
> > put_device(&rproc->dev);
> > }
> > EXPORT_SYMBOL(rproc_put);
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2024-01-29 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 22:11 [PATCH v4 0/2] remoteproc: get rproc devices for clusters Tanmay Shah
2024-01-03 22:11 ` [PATCH v4 1/2] remoteproc: Make rproc_get_by_phandle() work " Tanmay Shah
2024-01-15 18:14 ` Mathieu Poirier
2024-01-26 17:33 ` Bjorn Andersson
2024-01-03 22:11 ` [PATCH v4 2/2] remoteproc: enhance rproc_put() " Tanmay Shah
2024-01-26 17:38 ` Bjorn Andersson
2024-01-29 17:43 ` Tanmay Shah [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=ef007d96-4aa6-4e29-bbe6-3d6cb82475ba@amd.com \
--to=tanmay.shah@amd.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=tarak.reddy@amd.com \
/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