From: Greg KH <gregkh@linuxfoundation.org>
To: Russ Weight <russell.h.weight@intel.com>
Cc: Moritz Fischer <mdf@kernel.org>,
linux-fpga@vger.kernel.org, Xu Yilun <yilun.xu@intel.com>
Subject: Re: [PATCH 2/8] fpga: stratix10-soc: Add missing fpga_mgr_free() call
Date: Tue, 15 Jun 2021 09:16:28 +0200 [thread overview]
Message-ID: <YMhTzHNQV/iYHUJr@kroah.com> (raw)
In-Reply-To: <e7aef991-cd78-15fd-fdc9-9b75709af8c7@intel.com>
On Mon, Jun 14, 2021 at 10:38:01AM -0700, Russ Weight wrote:
>
>
> On 6/14/21 10:30 AM, Greg KH wrote:
> > On Mon, Jun 14, 2021 at 10:09:03AM -0700, Moritz Fischer wrote:
> >> From: Russ Weight <russell.h.weight@intel.com>
> >>
> >> The stratix10-soc driver uses fpga_mgr_create() function and is therefore
> >> responsible to call fpga_mgr_free() to release the class driver resources.
> >> Add a missing call to fpga_mgr_free in the s10_remove() function.
> >>
> >> Signed-off-by: Russ Weight <russell.h.weight@intel.com>
> >> Reviewed-by: Xu Yilun <yilun.xu@intel.com>
> >> Signed-off-by: Moritz Fischer <mdf@kernel.org>
> >> ---
> >> drivers/fpga/stratix10-soc.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/fpga/stratix10-soc.c b/drivers/fpga/stratix10-soc.c
> >> index 657a70c5fc99..9e34bbbce26e 100644
> >> --- a/drivers/fpga/stratix10-soc.c
> >> +++ b/drivers/fpga/stratix10-soc.c
> >> @@ -454,6 +454,7 @@ static int s10_remove(struct platform_device *pdev)
> >> struct s10_priv *priv = mgr->priv;
> >>
> >> fpga_mgr_unregister(mgr);
> >> + fpga_mgr_free(mgr);
> >> stratix10_svc_free_channel(priv->chan);
> >>
> >> return 0;
> >> --
> >> 2.31.1
> >>
> > Does this fix a specific commit? Does it need a Fixes: and cc: stable
> > line too?
> It fixes:
>
> e7eef1d7633a fpga: add intel stratix10 soc fpga manager driver
>
> And yes, I think it needs the Fixes: and cc: stable lines
>
> Moritz: Let me know if you want me to add the tags
>
> Greg: Patch 1 in this series could be viewed as a fix for a particular
> commit as well, but the code being deleted is harmless/unused. I'm
> assuming it does NOT need the Fixes: and cc: stable lines?
All patch 1 did is delete unused code, that doesn't really "fix"
anything that could be seen as a bug :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-15 7:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 17:09 [PATCH 0/8] FPGA Manager devres cleanup Moritz Fischer
2021-06-14 17:09 ` [PATCH 1/8] fpga: altera-pr-ip: Remove function alt_pr_unregister Moritz Fischer
2021-06-14 17:09 ` [PATCH 2/8] fpga: stratix10-soc: Add missing fpga_mgr_free() call Moritz Fischer
2021-06-14 17:30 ` Greg KH
2021-06-14 17:38 ` Russ Weight
2021-06-15 7:16 ` Greg KH [this message]
2021-06-14 17:40 ` Moritz Fischer
2021-06-15 7:28 ` Greg KH
2021-06-14 17:09 ` [PATCH 3/8] fpga: mgr: Rename dev to parent for parent device Moritz Fischer
2021-06-14 19:37 ` Tom Rix
2021-06-14 17:09 ` [PATCH 4/8] fpga: bridge: " Moritz Fischer
2021-06-14 17:09 ` [PATCH 5/8] fpga: region: " Moritz Fischer
2021-06-14 17:09 ` [PATCH 6/8] fpga: mgr: Use standard dev_release for class driver Moritz Fischer
2021-06-15 7:25 ` Greg KH
2021-06-15 16:00 ` Russ Weight
2021-06-14 17:09 ` [PATCH 7/8] fpga: bridge: " Moritz Fischer
2021-06-15 7:26 ` Greg KH
2021-06-14 17:09 ` [PATCH 8/8] fpga: region: " Moritz Fischer
2021-06-15 7:27 ` Greg KH
2021-06-15 7:30 ` [PATCH 0/8] FPGA Manager devres cleanup Greg KH
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=YMhTzHNQV/iYHUJr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=yilun.xu@intel.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;
as well as URLs for NNTP newsgroup(s).