linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>,
	bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] PCI: rcar-pcie: Fix memory leak
Date: Tue, 15 Aug 2017 17:56:35 +0200	[thread overview]
Message-ID: <20170815155634.GA21763@verge.net.au> (raw)
In-Reply-To: <20170814211114.GH32525@bhelgaas-glaptop.roam.corp.google.com>

On Mon, Aug 14, 2017 at 04:11:14PM -0500, Bjorn Helgaas wrote:
> On Fri, Aug 04, 2017 at 12:32:53PM +0900, Harunobu Kurokawa wrote:
> > When no PCIe card is inserted, there is a memory leak as
> > pci_free_resource_list is not called before returning.
> > 
> > v2:
> >  separate the patch to two files.
> > 
> > Harunobu Kurokawa (1):
> >   PCI: rcar-pcie: Fix memory leak when no PCIe card is inserted
> > 
> > Lorenzo Pieralisi (1):
> >   PCI: rcar: Fix error exit path
> > 
> >  drivers/pci/host/pcie-rcar.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> Waiting for Simon's ack...

Acked-by: Simon Horman <horms+renesas@verge.net.au>

  reply	other threads:[~2017-08-15 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  3:32 [PATCH v2 0/2] PCI: rcar-pcie: Fix memory leak Harunobu Kurokawa
2017-08-04  3:32 ` [PATCH v2 1/2] PCI: rcar: Fix error exit path Harunobu Kurokawa
2017-08-04  3:32 ` [PATCH v2 2/2] PCI: rcar-pcie: Fix memory leak when no PCIe card is inserted Harunobu Kurokawa
2017-08-14 21:11 ` [PATCH v2 0/2] PCI: rcar-pcie: Fix memory leak Bjorn Helgaas
2017-08-15 15:56   ` Simon Horman [this message]
2017-08-15 22:53 ` Bjorn Helgaas

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=20170815155634.GA21763@verge.net.au \
    --to=horms@verge.net.au \
    --cc=bhelgaas@google.com \
    --cc=harunobu.kurokawa.dn@renesas.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@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 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).