From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Tony Luck <tony.luck@intel.com>,
linuxppc-dev@ozlabs.org, linux-pci@vger.kernel.org,
Peter Haight <peterh@sapros.com>, Gary Hade <garyhade@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-am33-list@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yinghai@kernel.org>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH v4 1/5] PCI: split up pci_read_bridge_bases()
Date: Mon, 22 Feb 2010 16:23:56 -0800 [thread overview]
Message-ID: <20100222162356.2e4b3a19@jbarnes-piketon> (raw)
In-Reply-To: <20100217201952.4013.62534.stgit@bob.kio>
On Wed, 17 Feb 2010 13:19:52 -0700
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>
> No functional change; this breaks up pci_read_bridge_bases() into separate
> pieces for the I/O, memory, and prefetchable memory windows, similar to how
> Yinghai recently split up pci_setup_bridge() in 68e84ff3bdc.
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> ---
Applied this series, thanks Bjorn. Hopefully this one will
successfully run the linux-next gauntlet too. :)
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-02-23 0:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 20:19 [PATCH v4 0/5] PCI: try "pci=use_crs" again Bjorn Helgaas
2010-02-17 20:19 ` [PATCH v4 1/5] PCI: split up pci_read_bridge_bases() Bjorn Helgaas
2010-02-23 0:23 ` Jesse Barnes [this message]
2010-02-23 1:13 ` Jesse Barnes
2010-02-17 20:19 ` [PATCH v4 2/5] PCI: read bridge windows before filling in subtractive decode resources Bjorn Helgaas
2010-02-17 20:20 ` [PATCH v4 3/5] PCI: add pci_bus_for_each_resource(), remove direct bus->resource[] refs Bjorn Helgaas
2010-02-17 20:20 ` [PATCH v4 4/5] PCI: augment bus resource table with a list Bjorn Helgaas
2010-02-23 16:08 ` Bjorn Helgaas
2010-02-17 20:20 ` [PATCH v4 5/5] x86/PCI: use host bridge _CRS info by default on 2008 and newer machines Bjorn Helgaas
2010-02-19 0:58 ` [PATCH v4 0/5] PCI: try "pci=use_crs" again Gary Hade
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=20100222162356.2e4b3a19@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=Larry.Finger@lwfinger.net \
--cc=bjorn.helgaas@hp.com \
--cc=garyhade@us.ibm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=peterh@sapros.com \
--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).