From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Rob Herring <robh@kernel.org>,
Joao Pinto <Joao.Pinto@synopsys.com>,
linux-pci@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-renesas-soc@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Ryder Lee <ryder.lee@mediatek.com>,
linux-mediatek@lists.infradead.org,
Tanmay Inamdar <tinamdar@apm.com>,
Jingoo Han <jingoohan1@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] Fix PCI I/O space page leaks
Date: Mon, 16 Jul 2018 16:06:06 +0100 [thread overview]
Message-ID: <20180716150606.GA19945@red-moon> (raw)
In-Reply-To: <3e862a05-084a-d732-3060-6e2b234e9718@cogentembedded.com>
On Sun, Jul 15, 2018 at 07:00:21PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> Here's a set of 8 patches against the 'pci/controller-fixes' branch of Lorenzo
> Pieralisi's 'pci.git' repo. They are the fixes for the PCI I/O space page leaks
> (and the kernel BUG caused by them on deferred probe); those were 1st found
> testing the R-Car PCIe driver. The patches are in the chronological order
> (considering the date/time of the commits specified in the Fixes: tag), patches
> #2..#8 depend on the patch #1 in order to build/work as it introduces the managed
> device API that they all use...
>
> [1/8] PCI: xgene: Fix I/O space page leak
> [2/8] PCI: of: Fix I/O space page leak
> [3/8] PCI: versatile: Fix I/O space page leak
> [4/8] PCI: designware: Fix I/O space page leak
> [5/8] PCI: aardvark: Fix I/O space page leak
> [6/8] PCI: faraday: Fix I/O space page leak
> [7/8] PCI: mediatek: Fix I/O space page leak
> [8/8] PCI: v3-semi: Fix I/O space page leak
>
> MBR, Sergei
Hi Sergei,
I reshuffled the series, rewrote commit logs and move the devm_
API to commit 2 which is the one you tested AFAIK.
I pushed them out to my pci/controller-fixes branch which I hope
we can still aim for an -rc, please do have a look and let me know
what you think, I have not asked Bjorn to pull it yet.
Thanks,
Lorenzo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-07-16 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 16:00 [PATCH 0/8] Fix PCI I/O space page leaks Sergei Shtylyov
2018-07-15 16:03 ` [PATCH 1/8] PCI: xgene: Fix I/O space page leak Sergei Shtylyov
2018-07-15 16:06 ` [PATCH 2/8] PCI: of: " Sergei Shtylyov
2018-07-15 16:08 ` [PATCH 3/8] PCI: versatile: " Sergei Shtylyov
2018-07-15 16:13 ` [PATCH 4/8] PCI: designware: " Sergei Shtylyov
2018-07-15 16:23 ` [PATCH 5/8] PCI: aardvark: " Sergei Shtylyov
2018-07-15 16:28 ` [PATCH 6/8] PCI: faraday: " Sergei Shtylyov
2018-07-15 16:31 ` [PATCH 7/8] PCI: mediatek: " Sergei Shtylyov
2018-07-15 16:34 ` [PATCH 8/8] PCI: v3-semi: " Sergei Shtylyov
2018-07-16 15:06 ` Lorenzo Pieralisi [this message]
2018-07-16 18:50 ` [PATCH 0/8] Fix PCI I/O space page leaks Sergei Shtylyov
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=20180716150606.GA19945@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tinamdar@apm.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).