From: Will Deacon <will.deacon@arm.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"jgunthorpe@obsidianresearch.com"
<jgunthorpe@obsidianresearch.com>
Subject: Re: [GIT PULL] Generic PCI host controller driver for 3.16
Date: Thu, 29 May 2014 09:25:47 +0100 [thread overview]
Message-ID: <20140529082546.GH29812@arm.com> (raw)
In-Reply-To: <20140528205956.GU11907@google.com>
On Wed, May 28, 2014 at 09:59:56PM +0100, Bjorn Helgaas wrote:
> On Tue, May 27, 2014 at 11:40:51PM +0100, Will Deacon wrote:
> > Please can you pull my generic PCI host controller driver for 3.16?
> >
> > It's been doing the rounds on the lists for some time and things have
> > settled down now, despite a recent failed attempt at factoring out the
> > configuration space accessors.
>
> Is this the same as patches 2 & 3 of your v7 series of May 23?
Yes, they're identical so you can just pick the two patches from there if
you prefer.
> The only thing I see that is actually ARM-specific is the
> pci_common_init_dev() call and struct hw_pci usage. That makes sense at
> this stage of development. Maybe someday we'll be able to abstract this
> enough to make it truly arch-agnostic.
Indeed. I'm hoping Liviu continues with his PCI work for arm64, then I can
port this driver over to that eventually.
Cheers,
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Generic PCI host controller driver for 3.16
Date: Thu, 29 May 2014 09:25:47 +0100 [thread overview]
Message-ID: <20140529082546.GH29812@arm.com> (raw)
In-Reply-To: <20140528205956.GU11907@google.com>
On Wed, May 28, 2014 at 09:59:56PM +0100, Bjorn Helgaas wrote:
> On Tue, May 27, 2014 at 11:40:51PM +0100, Will Deacon wrote:
> > Please can you pull my generic PCI host controller driver for 3.16?
> >
> > It's been doing the rounds on the lists for some time and things have
> > settled down now, despite a recent failed attempt at factoring out the
> > configuration space accessors.
>
> Is this the same as patches 2 & 3 of your v7 series of May 23?
Yes, they're identical so you can just pick the two patches from there if
you prefer.
> The only thing I see that is actually ARM-specific is the
> pci_common_init_dev() call and struct hw_pci usage. That makes sense at
> this stage of development. Maybe someday we'll be able to abstract this
> enough to make it truly arch-agnostic.
Indeed. I'm hoping Liviu continues with his PCI work for arm64, then I can
port this driver over to that eventually.
Cheers,
Will
next prev parent reply other threads:[~2014-05-29 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 22:40 [GIT PULL] Generic PCI host controller driver for 3.16 Will Deacon
2014-05-27 22:40 ` Will Deacon
2014-05-28 20:59 ` Bjorn Helgaas
2014-05-28 20:59 ` Bjorn Helgaas
2014-05-29 8:25 ` Will Deacon [this message]
2014-05-29 8:25 ` Will Deacon
2014-05-29 22:13 ` Bjorn Helgaas
2014-05-29 22:13 ` 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=20140529082546.GH29812@arm.com \
--to=will.deacon@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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.