From: Stephen Warren <swarren@wwwdotorg.org>
To: Jiang Liu <liuj97@gmail.com>,
Thierry Reding <thierry.reding@avionic-design.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Don Dutile <ddutile@redhat.com>, Colin Cross <ccross@android.com>,
Olof Johansson <olof@lixom.net>, Jiang Liu <jiang.liu@huawei.com>,
Yinghai Lu <yinghai@kernel.org>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
"Rafael J . Wysocki" <rjw@sisk.pl>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Yijing Wang <wangyijing@huawei.com>,
Russell King <linux@arm.linux.org.uk>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 12/32] PCI/ARM: use PCIe capabilities access functions to simplify implementation
Date: Wed, 01 Aug 2012 11:20:13 -0600 [thread overview]
Message-ID: <5019654D.2000408@wwwdotorg.org> (raw)
In-Reply-To: <1343836477-7287-13-git-send-email-jiang.liu@huawei.com>
On 08/01/2012 09:54 AM, Jiang Liu wrote:
> From: Jiang Liu <jiang.liu@huawei.com>
>
> Use PCIe capabilities access functions to simplify PCIe ARM implementation.
>
> Signed-off-by: Jiang Liu <liuj97@gmail.com>
This is probably fine from my perspective assuming the underlying PCI
API implementation is OKd by relevant people.
Thierry, can you comment on whether this will conflict with your Tegra
PCIe driver series? If it doesn't, this patch can go through any
relevant PCI tree. If it does, we may have to take this through the
Tegra tree after merging the dependencies, or defer it to later.
next prev parent reply other threads:[~2012-08-01 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1343836477-7287-1-git-send-email-jiang.liu@huawei.com>
2012-08-01 15:54 ` [PATCH v3 12/32] PCI/ARM: use PCIe capabilities access functions to simplify implementation Jiang Liu
2012-08-01 17:20 ` Stephen Warren [this message]
2012-08-02 5:58 ` Thierry Reding
[not found] ` <1343836477-7287-13-git-send-email-jiang.liu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2012-08-03 18:05 ` Stephen Warren
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=5019654D.2000408@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bhelgaas@google.com \
--cc=ccross@android.com \
--cc=ddutile@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=liuj97@gmail.com \
--cc=olof@lixom.net \
--cc=rjw@sisk.pl \
--cc=thierry.reding@avionic-design.de \
--cc=wangyijing@huawei.com \
--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