From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Fix PCI I/O space page leaks
Date: Mon, 16 Jul 2018 21:50:52 +0300 [thread overview]
Message-ID: <db85a353-2d90-2aa5-2f45-13d8a0b36424@cogentembedded.com> (raw)
In-Reply-To: <20180716150606.GA19945@red-moon>
On 07/16/2018 06:06 PM, Lorenzo Pieralisi wrote:
>> 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.
Well, that means the XGene fix wouldn't propagate "deep enough", if that's your
choice, OK...
> 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.
Your edits generally look fine, except you forgot the usual "X has the same issue"
phrase in the XGene's commit log.
> Thanks,
> Lorenzo
MBR, Sergei
prev parent reply other threads:[~2018-07-16 18:50 UTC|newest]
Thread overview: 7+ 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:08 ` [PATCH 3/8] PCI: versatile: " Sergei Shtylyov
2018-07-15 16:23 ` [PATCH 5/8] PCI: aardvark: " Sergei Shtylyov
2018-07-15 16:31 ` [PATCH 7/8] PCI: mediatek: " Sergei Shtylyov
2018-07-16 15:06 ` [PATCH 0/8] Fix PCI I/O space page leaks Lorenzo Pieralisi
2018-07-16 18:50 ` Sergei Shtylyov [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=db85a353-2d90-2aa5-2f45-13d8a0b36424@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.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).