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>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
Peter Haight <peterh@sapros.com>, Gary Hade <garyhade@us.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-am33-list@redhat.com, Yinghai Lu <yinghai@kernel.org>,
linux-alpha@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH v3 1/7] PCI: split up pci_read_bridge_bases()
Date: Fri, 12 Feb 2010 13:26:23 -0800 [thread overview]
Message-ID: <20100212132623.79fdf5cd@jbarnes-piketon> (raw)
In-Reply-To: <20100212165952.19522.19555.stgit@bob.kio>
On Fri, 12 Feb 2010 09:59: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 to my linux-next branch replacing the old ones, thanks Bjorn.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-02-12 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 16:59 [PATCH v3 0/7] PCI: try "pci=use_crs" again Bjorn Helgaas
2010-02-12 16:59 ` [PATCH v3 1/7] PCI: split up pci_read_bridge_bases() Bjorn Helgaas
2010-02-12 21:26 ` Jesse Barnes [this message]
2010-02-12 16:59 ` [PATCH v3 2/7] PCI: read bridge windows before filling in subtractive decode resources Bjorn Helgaas
2010-02-12 17:00 ` [PATCH v3 3/7] PCI: replace bus resource table with a list Bjorn Helgaas
2010-02-12 17:00 ` [PATCH v3 4/7] x86/PCI: use host bridge _CRS info by default on 2008 and newer machines Bjorn Helgaas
2010-02-12 17:00 ` [PATCH v3 5/7] PCI: make disabled window printk style match the enabled ones Bjorn Helgaas
2010-02-12 17:00 ` [PATCH v3 6/7] PCI: break out primary/secondary/subordinate for readability Bjorn Helgaas
2010-02-12 17:00 ` [PATCH v3 7/7] PCI: reference bridge window resources explicitly Bjorn Helgaas
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=20100212132623.79fdf5cd@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-alpha@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