From: Bjorn Helgaas <bhelgaas@google.com>
To: Zhou Wang <wangzhou1@hisilicon.com>
Cc: Mohit Kumar <mohit.kumar@st.com>,
Jingoo Han <jg1.han@samsung.com>, Arnd Bergmann <arnd@arndb.de>,
Liviu Dudau <Liviu.Dudau@arm.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, gabriele.paoloni@huawei.com,
yuanzhichang@hisilicon.com, zhudacai@hisilicon.com,
zhangjukuo@huawei.com, xiehaitao@huawei.com,
liguozhu@hisilicon.com, wangzhou.bry@gmail.com
Subject: Re: [RFC PATCH 0/3] PCI: host: Add PCIe host support for Hisilicon Soc Hip05
Date: Thu, 7 May 2015 10:24:18 -0500 [thread overview]
Message-ID: <20150507152418.GM24643@google.com> (raw)
In-Reply-To: <1429077843-184462-1-git-send-email-wangzhou1@hisilicon.com>
On Wed, Apr 15, 2015 at 02:04:00PM +0800, Zhou Wang wrote:
> This patchset adds PCIe host support for Hisilicon Soc Hip05. The PCIe hosts
> use PCIe IP core from Synopsys. So the driver is based on designware PCIe driver.
>
> Zhou Wang (3):
> PCI: host: designware: support ARM64
> PCI: Host: Add PCIe host support for Hisilicon Soc Hip05
> Documentation: devicetree: Add hisilicon PCIe host binding
Please run "git log" and "git log --oneline" on each file you change, and
make your changelogs and summaries look like the rest -- same style, same
capitalization, etc.
> .../devicetree/bindings/pci/hisilicon-pcie.txt | 46 ++++
> drivers/pci/host/Kconfig | 5 +
> drivers/pci/host/Makefile | 1 +
> drivers/pci/host/pcie-designware.c | 44 +++-
> drivers/pci/host/pcie-hisi.c | 252 +++++++++++++++++++++
> 5 files changed, 345 insertions(+), 3 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
> create mode 100644 drivers/pci/host/pcie-hisi.c
>
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-05-07 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 6:04 [RFC PATCH 0/3] PCI: host: Add PCIe host support for Hisilicon Soc Hip05 Zhou Wang
[not found] ` <1429077843-184462-1-git-send-email-wangzhou1-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2015-04-15 6:04 ` [RFC PATCH 1/3] PCI: host: designware: support ARM64 Zhou Wang
2015-04-15 10:04 ` Arnd Bergmann
2015-04-16 5:51 ` Zhou Wang
2015-04-16 8:00 ` Arnd Bergmann
2015-04-15 6:04 ` [RFC PATCH 2/3] PCI: Host: Add PCIe host support for Hisilicon Soc Hip05 Zhou Wang
2015-04-15 6:04 ` [RFC PATCH 3/3] Documentation: devicetree: Add hisilicon PCIe host binding Zhou Wang
2015-05-07 15:24 ` Bjorn Helgaas [this message]
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=20150507152418.GM24643@google.com \
--to=bhelgaas@google.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gabriele.paoloni@huawei.com \
--cc=jg1.han@samsung.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=mohit.kumar@st.com \
--cc=wangzhou.bry@gmail.com \
--cc=wangzhou1@hisilicon.com \
--cc=xiehaitao@huawei.com \
--cc=yuanzhichang@hisilicon.com \
--cc=zhangjukuo@huawei.com \
--cc=zhudacai@hisilicon.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).