Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754032AbdGCMz0 (ORCPT ); Mon, 3 Jul 2017 08:55:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:54436 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752241AbdGCMzX (ORCPT ); Mon, 3 Jul 2017 08:55:23 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BE9D422BCC Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=helgaas@kernel.org Date: Mon, 3 Jul 2017 07:55:20 -0500 From: Bjorn Helgaas To: Will Deacon Cc: Xiaowei Song , guodong.xu@linaro.org, bhelgaas@google.com, robh+dt@kernel.org, suzhuangluan@hisilicon.com, linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Catalin Marinas , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v11 0/3]add PCIe driver for Kirin PCIe Message-ID: <20170703125520.GA13824@bhelgaas-glaptop.roam.corp.google.com> References: <20170619102349.50652-1-songxiaowei@hisilicon.com> <20170702233657.GA13507@bhelgaas-glaptop.roam.corp.google.com> <20170703104727.GB1573@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170703104727.GB1573@arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 834 Lines: 20 On Mon, Jul 03, 2017 at 11:47:27AM +0100, 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. OK, dropped the defconfig change and updated my -next branch. I'm still looking for a MAINTAINERS update.