From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Jingoo Han <jingoohan1@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH v3 0/8] PCI: leak fixes, removable generic PCI host, assorted stuff
Date: Tue, 15 May 2018 10:39:30 +0200 [thread overview]
Message-ID: <8f40ba94-d730-5f45-c113-2cd53c722467@siemens.com> (raw)
In-Reply-To: <72f23e5f-4641-9ef3-09e6-70c4724f21a4@mentor.com>
On 2018-05-15 09:58, Vladimir Zapolskiy wrote:
> Hi Jan,
>
> On 05/15/2018 08:58 AM, Jan Kiszka wrote:
>> Changes in v3:
>> - refactor series to be both bisectable and simpler while reworking
>> of_pci_get_host_bridge_resources()
>> - include of_pci_get_host_bridge_resources() removal
>> - include devm_of_pci_get_host_bridge_resources() error path fixes
>> - effectively, no functional changes to v2
>
> while the previous version of the changeset plus the fixup found on Bjorn's
> pci/resource branch is sufficient, I can't argue with the fact that this
> series is way better.
0day-testing found a build breakage in the middle of the old series.
Wasn't straightforward to fix, so Bjorn suggested a different series
structure which I try to implement with v3.
>
> In case if this series is accepted I'll review and test the fix of
> of_pci_get_host_bridge_resources() memleak again, no worries.
Thanks, will address that issue first.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-05-15 8:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 5:58 Jan Kiszka
2018-05-15 5:58 ` [PATCH v3 1/8] PCI: Make pci_get_new_domain_nr() static Jan Kiszka
2018-05-15 5:58 ` [PATCH v3 2/8] PCI: Fix memory leak of devm_pci_alloc_host_bridge() Jan Kiszka
2018-05-15 5:58 ` [PATCH v3 3/8] PCI: Rename device node parameter of of_pci_get_host_bridge_resources() Jan Kiszka
2018-05-15 7:58 ` Vladimir Zapolskiy
2018-05-15 5:58 ` [PATCH v3 4/8] PCI: Replace dev_node parameter of of_pci_get_host_bridge_resources with device Jan Kiszka
2018-05-15 7:54 ` Vladimir Zapolskiy
2018-05-15 5:58 ` [PATCH v3 5/8] PCI: Replace pr_*() with dev_*() in of_pci_get_host_bridge_resources() Jan Kiszka
2018-05-15 7:57 ` Vladimir Zapolskiy
2018-05-15 5:58 ` [PATCH v3 6/8] PCI: Rework of_pci_get_host_bridge_resources() to devm_of_pci_get_host_bridge_resources() Jan Kiszka
2018-05-15 7:54 ` Vladimir Zapolskiy
2018-05-15 8:36 ` Jan Kiszka
2018-05-15 5:58 ` [PATCH v3 7/8] PCI: Add support for unbinding the generic PCI host controller Jan Kiszka
2018-05-15 5:58 ` [PATCH v3 8/8] PCI: Enable PCI_DOMAINS along with " Jan Kiszka
2018-05-15 7:58 ` [PATCH v3 0/8] PCI: leak fixes, removable generic PCI host, assorted stuff Vladimir Zapolskiy
2018-05-15 8:39 ` Jan Kiszka [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=8f40ba94-d730-5f45-c113-2cd53c722467@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=vladimir_zapolskiy@mentor.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®