From: Wei Xu <xuwei5@hisilicon.com>
To: Guodong Xu <guodong.xu@linaro.org>
Cc: devicetree@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-pci <linux-pci@vger.kernel.org>,
Suzhuangluan <suzhuangluan@hisilicon.com>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Xiaowei Song <songxiaowei@hisilicon.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v11 0/3]add PCIe driver for Kirin PCIe
Date: Mon, 3 Jul 2017 14:32:24 +0100 [thread overview]
Message-ID: <595A4768.20404@hisilicon.com> (raw)
In-Reply-To: <CAFGCpxx+92PSs1VaryFOXau7CjBYEP4H6wT-o=bNMwkSznjQuw@mail.gmail.com>
Hi Guodong,
On 2017/7/3 14:04, Guodong Xu wrote:
> Hi, Xu Wei
>
>
>
> On Mon, Jul 3, 2017 at 6:47 PM, Will Deacon <will.deacon@arm.com> wrote:
>> On Sun, Jul 02, 2017 at 06:36:57PM -0500, Bjorn Helgaas wrote:
>>> [+cc Catalin, Will, linux-arm-kernel]
>>>
>>> Applied patches 2 & 3 to pci/host-kirin for v4.13.
>>>
>>> I would like a MAINTAINERS update, too. If you send me that, I'll
>>> squash it into the driver patch.
>>>
>>> Catalin, Will, how do you want to handle the
>>> arch/arm64/configs/defconfig change (patch 3)? It's currently on my
>>> branch, but I'm happy to drop it if another route is better.
>>
>> defconfig updates usually go through arm-soc, via the relevant platform
>> maintainer, so it would be best to follow that route here too otherwise
>> you'll probably see conflicts in -next.
>>
>
> Is it ok for you to pick up the arch/arm64/configs/defconfig change (patch 3)?
Since it is already 4.12-rc7, I will pick up it and queue for the v4.14.
Are you fine about that?
Thanks!
Best Regards,
Wei
>
> -Guodong
>
>> Will
>
> .
>
next prev parent reply other threads:[~2017-07-03 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 10:23 [PATCH v11 0/3]add PCIe driver for Kirin PCIe Xiaowei Song
2017-06-19 10:23 ` [PATCH v11 1/3] PCI: hisi: Add DT binding for PCIe of Kirin SoC series Xiaowei Song
[not found] ` <20170619102349.50652-2-songxiaowei-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2017-06-19 10:44 ` Wei Xu
2017-06-19 10:50 ` Wei Xu
2017-06-19 10:23 ` [PATCH v11 2/3] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC Xiaowei Song
[not found] ` <20170619102349.50652-3-songxiaowei-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2017-06-26 14:01 ` Guodong Xu
2017-06-19 10:23 ` [PATCH v11 3/3] ARM4: defconfig: Enable Kirin PCIe Xiaowei Song
2017-07-02 23:36 ` [PATCH v11 0/3]add PCIe driver for " Bjorn Helgaas
[not found] ` <20170702233657.GA13507-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org>
2017-07-03 10:47 ` Will Deacon
[not found] ` <20170703104727.GB1573-5wv7dgnIgG8@public.gmane.org>
2017-07-03 12:55 ` Bjorn Helgaas
2017-07-03 13:04 ` Guodong Xu
2017-07-03 13:32 ` Wei Xu [this message]
[not found] ` <595A4768.20404-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2017-07-04 2:03 ` Guodong Xu
2017-08-15 13:28 ` Wei Xu
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=595A4768.20404@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=guodong.xu@linaro.org \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=songxiaowei@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=will.deacon@arm.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).