From: Bjorn Helgaas <bhelgaas@google.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Frank Li <lznuaa@gmail.com>, Shawn Guo <shawn.guo@linaro.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Jingoo Han <jg1.han@samsung.com>,
Thierry Reding <thierry.reding@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Kevin Hilman <khilman@linaro.org>,
Stephen Warren <swarren@nvidia.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PCI host merge strategy and maintainers
Date: Fri, 27 Sep 2013 12:58:26 -0600 [thread overview]
Message-ID: <CAErSpo5tN==4nSv2u3SUBe_L4VsWn4P7TN+LtrC172Qj1vhtog@mail.gmail.com> (raw)
In-Reply-To: <20130926150228.GL11119@titan.lakedaemon.net>
On Thu, Sep 26, 2013 at 9:02 AM, Jason Cooper <jason@lakedaemon.net> wrote:
> On Wed, Sep 25, 2013 at 05:28:28PM -0600, Bjorn Helgaas wrote:
>> There are patches for exynos, imx6, mvebu, and tegra on the PCI list,
>> and I want to sort out how people expect them to be merged.
>>
>> My current assumption is the following:
> ...
>> drivers/pci/host/pci-mvebu.c ?? unclear; Jason Cooper has merged
>> some, I've merged some
...
> Well, there's nothing new here, so if you're ok with me taking them,
> I'll continue on that path for these two series.
OK, I'll assume Jason will take care of pci-mvebu.c, and I will merge
changes to everything else via the PCI tree. I will still wait for
acks from the following before merging things:
designware: Jingoo Han <jg1.han@samsung.com>
exynos: Jingoo Han <jg1.han@samsung.com>
imx6: Shawn Guo <shawn.guo@linaro.org>
tegra: Thierry Reding <thierry.reding@gmail.com>
Bjorn
next prev parent reply other threads:[~2013-09-27 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 23:28 PCI host merge strategy and maintainers Bjorn Helgaas
2013-09-26 2:32 ` Shawn Guo
2013-09-26 15:02 ` Jason Cooper
2013-09-27 18:58 ` Bjorn Helgaas [this message]
2013-09-27 19:19 ` Frank Li
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='CAErSpo5tN==4nSv2u3SUBe_L4VsWn4P7TN+LtrC172Qj1vhtog@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jg1.han@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=thomas.petazzoni@free-electrons.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 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).