From: Bjorn Helgaas <bhelgaas@google.com>
To: Andreas Noever <andreas.noever@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/8] PCI: cleanup pci_scan_bridge
Date: Mon, 10 Feb 2014 17:16:24 -0700 [thread overview]
Message-ID: <20140211001624.GA12851@google.com> (raw)
In-Reply-To: <1390510768-5652-1-git-send-email-andreas.noever@gmail.com>
On Thu, Jan 23, 2014 at 09:59:20PM +0100, Andreas Noever wrote:
> I have been reading the code around pci_scan_bridge and noticed a few oddities.
> These patches try to cleanup some of the these things.
>
> Most of the patches make also sense in isolation, but some make more sense with
> the previous ones applied as well. None of the patches fix any observed bugs.
> Patch 5 fixes a (probably harmless) dmesg.
>
> The changes related to CardBus probing are completely untested.
>
> Andreas
>
> Andreas Noever (8):
> PCI: Increment max correctly in pci_scan_bridge.
> PCI: Clarify the "scan anyway" comment in pci_scan_bridge.
> PCI: Assign CardBus bus number only during the second pass.
> PCI: Use request_resource_conflict instead of insert_ for bus numbers.
> PCI: Make sure bus number resources stay within their parents bounds.
> PCI: Remove pci_fixup_parent_subordinate_busnr.
> PCI: Check for child busses which use more bus numbers than allocated.
> PCI: Don't scan random busses in pci_scan_bridge.
>
> drivers/pci/probe.c | 78 +++++++++++++++++++++--------------------------------
> 1 file changed, 31 insertions(+), 47 deletions(-)
I applied all these to pci/scan-bridge for v3.15, thanks!
Bjorn
prev parent reply other threads:[~2014-02-11 0:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 20:59 [PATCH 0/8] PCI: cleanup pci_scan_bridge Andreas Noever
2014-01-23 20:59 ` [PATCH 1/8] PCI: Increment max correctly in pci_scan_bridge Andreas Noever
2014-01-23 20:59 ` [PATCH 2/8] PCI: Clarify the "scan anyway" comment " Andreas Noever
2014-01-23 20:59 ` [PATCH 3/8] PCI: Assign CardBus bus number only during the second pass Andreas Noever
2014-01-23 20:59 ` [PATCH 4/8] PCI: Use request_resource_conflict instead of insert_ for bus numbers Andreas Noever
2014-01-23 20:59 ` [PATCH 5/8] PCI: Make sure bus number resources stay within their parents bounds Andreas Noever
2014-01-23 20:59 ` [PATCH 6/8] PCI: Remove pci_fixup_parent_subordinate_busnr Andreas Noever
2014-01-23 20:59 ` [PATCH 7/8] PCI: Check for child busses which use more bus numbers than allocated Andreas Noever
2014-01-23 20:59 ` [PATCH 8/8] PCI: Don't scan random busses in pci_scan_bridge Andreas Noever
2014-02-11 0:16 ` Bjorn Helgaas [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=20140211001624.GA12851@google.com \
--to=bhelgaas@google.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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).