Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933977AbdGCNuf (ORCPT ); Mon, 3 Jul 2017 09:50:35 -0400 Received: from szxga01-in.huawei.com ([45.249.212.187]:9268 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933263AbdGCNua (ORCPT ); Mon, 3 Jul 2017 09:50:30 -0400 Subject: Re: [PATCH v11 0/3]add PCIe driver for Kirin PCIe To: Guodong Xu References: <20170619102349.50652-1-songxiaowei@hisilicon.com> <20170702233657.GA13507@bhelgaas-glaptop.roam.corp.google.com> <20170703104727.GB1573@arm.com> CC: Bjorn Helgaas , Xiaowei Song , Bjorn Helgaas , Rob Herring , Suzhuangluan , linux-pci , , "linux-kernel@vger.kernel.org" , "Catalin Marinas" , linux-arm-kernel , Will Deacon From: Wei Xu Message-ID: <595A4768.20404@hisilicon.com> Date: Mon, 3 Jul 2017 14:32:24 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.203.181.153] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.595A4779.00A3,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 27f4fbbcbdba12ee317706f9c66c126a Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 41 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 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 > > . >