From: Yinghai Lu <yinghai@kernel.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [RFC PATCH] methods to access resources of a struct pci_dev
Date: Mon, 18 Jun 2012 19:57:16 -0700 [thread overview]
Message-ID: <CAE9FiQUAGfXppTWwgbCEui9jFd3f75Fi4X-AvUkT0z3TNuqwyw@mail.gmail.com> (raw)
In-Reply-To: <20120619014642.GA2310@ram-ThinkPad-T61>
On Mon, Jun 18, 2012 at 6:46 PM, Ram Pai <linuxram@us.ibm.com> wrote:
> On Mon, Jun 18, 2012 at 11:30:13AM -0700, Yinghai Lu wrote:
>> I have patchset on this, please check
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
>> for-pci-for-each-res-addon
>>
>
>
> Amazing, when are you pushing those patches in? Looks like you have
> patches for everything :)
>
> Do you also have patches that change all the places that directly access
> the ->resource structure?
maybe not. could still have some left over.
>
> Also does Bjorn pull regularly from your tree? Is making patches
> against your tree the right approach?
No.
Bjorn will get patches from my branch and have to update change log at least.
and then into pci/next.
current still have several branch in the waiting list
for-pci-res-alloc
for-pci-busn-alloc
for-pci-root-bus-hotplug
for-pci-for-each-res-addon
also for-x86-irq and for-iommu are for pci root bus hotplug related too, but
need to push them to tip pci related get merged.
Current status: for-pci-busn-alloc is pending with
http://git.kernel.org/?p=linux/kernel/git/yinghai/linux-yinghai.git;a=patch;h=b00469b377231ebe0b76248ec6d1866b51966c97
Bjorn thought that is too complicated.
Thanks
Yinghai
next prev parent reply other threads:[~2012-06-19 2:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 5:03 [RFC PATCH] methods to access resources of a struct pci_dev Ram Pai
2012-06-18 18:30 ` Yinghai Lu
2012-06-19 1:46 ` Ram Pai
2012-06-19 2:57 ` Yinghai Lu [this message]
2012-08-15 21:25 ` Bjorn Helgaas
2012-08-16 3:26 ` Ram Pai
2012-08-16 4:11 ` Yinghai Lu
2012-08-16 4:41 ` Ram Pai
2012-08-21 15:13 ` [RFC PATCH v2 ]pci: pci resource iterator Ram Pai
2012-08-21 23:22 ` Yinghai Lu
2012-08-22 10:15 ` Ram Pai
2012-08-22 17:31 ` Yinghai Lu
2012-08-22 17:35 ` Yinghai Lu
2012-08-23 0:28 ` Yinghai Lu
2012-08-23 5:09 ` [RFC PATCH v3 " Ram Pai
2012-08-23 19:30 ` Yinghai Lu
2012-08-27 7:33 ` Ram Pai
2012-09-03 8:07 ` Yinghai Lu
2012-09-03 9:08 ` Ram Pai
2012-09-03 18:20 ` Yinghai Lu
2012-09-04 3:27 ` Ram Pai
2012-09-18 0:03 ` Yinghai Lu
2012-09-21 6:18 ` Ram Pai
2012-09-21 6:27 ` 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=CAE9FiQUAGfXppTWwgbCEui9jFd3f75Fi4X-AvUkT0z3TNuqwyw@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxram@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.