From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Tony Luck <tony.luck@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/4] PCI: Add iobusn_resource and insert root bus range to that tree.
Date: Fri, 27 Jan 2012 10:29:41 -0800 [thread overview]
Message-ID: <20120127102941.22eb826f@jbarnes-desktop> (raw)
In-Reply-To: <1327360018-10929-2-git-send-email-yinghai@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Mon, 23 Jan 2012 15:06:55 -0800
Yinghai Lu <yinghai@kernel.org> wrote:
> now only root bus number range is in that tree.
>
> later every bus will have extra busn_res, and linked them toghter to iobusn_resource.
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> ---
This needs to be split into at least a few patches:
- one to add the bus resource tracking infrastructure to the core
- one to add tracking to the core
- one patch per arch
and acks and tested-bys from the arch folks.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-27 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 23:06 [PATCH 0/4] PCI: allocate pci bus num range for unassigned bridge busn Yinghai Lu
2012-01-23 23:06 ` [PATCH 1/4] PCI: Add iobusn_resource and insert root bus range to that tree Yinghai Lu
2012-01-27 18:29 ` Jesse Barnes [this message]
2012-01-23 23:06 ` [PATCH 2/4] PCI: Allocate bus range instead of use max blindly Yinghai Lu
2012-01-23 23:06 ` [PATCH 3/4] PCI: kill pci_fixup_parent_subordinate_busnr() Yinghai Lu
2012-01-23 23:06 ` [PATCH 4/4] PCI: Seperate child bus scanning to two passes overall Yinghai Lu
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=20120127102941.22eb826f@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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).