From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: pci_probe_only and bus_to_resources patches rebased to pci linux-next branch
Date: Fri, 24 Feb 2012 14:27:54 -0800 [thread overview]
Message-ID: <20120224142754.2fc00f7a@jbarnes-desktop> (raw)
In-Reply-To: <CAErSpo67Y4xtctJ=a8LQLqopRyM9_3gYKwFSUw8kT6XEVsPZzA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
On Thu, 23 Feb 2012 21:04:04 -0800
Bjorn Helgaas <bhelgaas@google.com> wrote:
> Hi Jesse,
>
> I rebased these series:
>
> v2 generic pci_probe_only flag
> (http://marc.info/?l=linux-pci&m=133002621016744&w=2)
>
> v2 add PCI bus-to-resource offset support in core
> (http://marc.info/?l=linux-pci&m=132884138928641&w=2)
>
> onto your current linux-next tree (based on commit 823806ff). Minor
> conflict resolutions in include/linux/pci.h, and that's about it.
>
> You can examine the result here:
>
> https://github.com/bjorn-helgaas/linux/tree/pci-next+probe_only+bus2res-fb127cb
>
> or pull both series with:
>
> git pull git://github.com/bjorn-helgaas/linux.git
> pci-next+probe_only+bus2res-fb127cb
Nice, I like all the deletions especially.
Pulled into linux-next.
--
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-02-24 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 5:04 pci_probe_only and bus_to_resources patches rebased to pci linux-next branch Bjorn Helgaas
2012-02-24 5:23 ` Yinghai Lu
2012-02-24 17:38 ` Bjorn Helgaas
2012-02-24 21:40 ` Bjorn Helgaas
2012-02-24 22:27 ` Jesse Barnes [this message]
2012-02-25 1:24 ` 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=20120224142754.2fc00f7a@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--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).