From: Bjorn Helgaas <helgaas@kernel.org>
To: Song Xiaowei <songxiaowei@hisilicon.com>
Cc: bhelgaas@google.com, kishon@ti.com, jingoohan1@gmail.com,
arnd@arndb.de, tn@semihalf.com, keith.busch@intel.com,
niklas.cassel@axis.com, dhdang@apm.com, liudongdong3@huawei.com,
puck.chen@hisilicon.com, guodong.xu@linaro.org,
wangbinghui@hisilicon.com, suzhuangluan@hisilicon.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
chenyao11@huawei.com
Subject: Re: [PATCH v4 2/3] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC
Date: Tue, 23 May 2017 16:30:32 -0500 [thread overview]
Message-ID: <20170523213032.GD15055@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20170518091640.36704-1-songxiaowei@hisilicon.com>
Hi,
When you repost this, would you mind posting the v4 as a complete separate
thread with a cover letter, i.e.,
[v4 0/3] cover
[v4 1/3] arm64: dts: hi3660: add pcie node
[v4 2/3] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC
[v4 3/3] defconfig: PCI: Enable Kirin PCIe defconfig
That makes it much easier to pull the patches out of email.
On Thu, May 18, 2017 at 05:16:40PM +0800, Song Xiaowei wrote:
> +/* info lacated in sysctrl */
s/lacated/located/
> +/*peri_crg ctrl*/
Add spaces after "/*" and before "*/" (also fix other occurrences below).
> +static int __init kirin_add_pcie_port(struct dw_pcie *pci,
> + struct platform_device *pdev)
> +{
> + int ret;
> +
> + pci->pp.ops = &kirin_pcie_host_ops;
> +
> + ret = dw_pcie_host_init(&pci->pp);
> +
> + return ret;
return dw_pcie_host_init(&pci->pp);
and get rid of "ret" altogether.
> +}
> + ret = kirin_add_pcie_port(pci, pdev);
> + if (ret)
> + return ret;
> +
> + return 0;
return kirin_add_pcie_port(pci, pdev);
> +}
prev parent reply other threads:[~2017-05-23 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 9:16 Song Xiaowei
2017-05-18 9:22 ` Niklas Cassel
2017-05-18 18:48 ` Jingoo Han
2017-05-23 21:30 ` 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=20170523213032.GD15055@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=chenyao11@huawei.com \
--cc=dhdang@apm.com \
--cc=guodong.xu@linaro.org \
--cc=jingoohan1@gmail.com \
--cc=keith.busch@intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=niklas.cassel@axis.com \
--cc=puck.chen@hisilicon.com \
--cc=songxiaowei@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=tn@semihalf.com \
--cc=wangbinghui@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
all inboxes | Powered by JetHome®