Received: by 2002:a25:1104:0:0:0:0:0 with SMTP id 4csp287678ybr; Fri, 22 May 2020 06:43:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw/Ff4+GiSJNEZTwJAXIj1ux591ZufTQC6Mx1lKWmlewUCzQCgA4GU8/MLnkZnqRRqP5sIX X-Received: by 2002:a17:906:44f:: with SMTP id e15mr7884418eja.161.1590154989914; Fri, 22 May 2020 06:43:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590154989; cv=none; d=google.com; s=arc-20160816; b=FDUj6vphC65bCTiYU19yQ2nH8Q1xcHdxkvp4qJiC4vftuUBF/4atOA90EdPGoFcmD3 CJhWD3VmdDuaUhFCkjn4D8cjkjVHI4j3y5sIWhZWeGj/PDMXvKTgRdVYf0YI0unVEfaK SyPNYtPd4AYwUbFjNd92lLrS2G/jmCwtywHpjrvyRLpqa3UkWhcOWDnTASB9rLmWEMdO YadB9RHHdgUEgnPlvpRq25Py9FTMxlXQBsyNq2MRuNhgaP6kpuDN1u8sSoSuYbk0xED2 /oHe3rQjRqAGYVDrrjajLphmeEUDL4ofM8kxVMsiNx6GW4dVUooq1eSNyFZAJVTsms0Q uFHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=r4u9QaXSDQhv/BD3qXkbl6i4ce2sJsoXIWnzh7I99y0=; b=dQ/sk67MfZDrYjM/ZjENmQnkkrC5eBSSG5DVQbNUyfTf7kSYjQfZFRM/9qm1WahJQx a3g9thXkjcD+WDrvnMFohbRkFTtlFtVj/NX61YcTLbC6N9azYei33dete+/ElsPg4NIa L90Y1wlIlYP52zrfP8LAday1iQ4qY2+TTwQX02HQI+q4+tf7eK3m23OSuYIYHFS8FpSW Kaq7t5q/oUzfs/nL0/U3kzFXWZr2R5HpIuUKf99y4Yz5BTBLjPOHCWmZw3HQ1pPPcHIi nS+ee/URDfQbYKED5auzPrtloyo3yMC7tfzkdk+qvqS7b493LaCnQf6CQ7hM7dm/a/jm /ZXQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a6si5622323ejy.11.2020.05.22.06.42.46; Fri, 22 May 2020 06:43:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729980AbgEVNky (ORCPT + 99 others); Fri, 22 May 2020 09:40:54 -0400 Received: from foss.arm.com ([217.140.110.172]:35854 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729399AbgEVNkx (ORCPT ); Fri, 22 May 2020 09:40:53 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 0BF121063; Fri, 22 May 2020 06:40:53 -0700 (PDT) Received: from e121166-lin.cambridge.arm.com (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 385DD3F68F; Fri, 22 May 2020 06:40:51 -0700 (PDT) Date: Fri, 22 May 2020 14:40:48 +0100 From: Lorenzo Pieralisi To: Jiaxun Yang Cc: linux-pci@vger.kernel.org, Rob Herring , Bjorn Helgaas , Rob Herring , Thomas Bogendoerfer , Huacai Chen , Paul Burton , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org Subject: Re: [PATCH v10 2/5] PCI: Add Loongson PCI Controller support Message-ID: <20200522134048.GG11785@e121166-lin.cambridge.arm.com> References: <20200427060551.1372591-1-jiaxun.yang@flygoat.com> <20200514131650.3587281-1-jiaxun.yang@flygoat.com> <20200514131650.3587281-2-jiaxun.yang@flygoat.com> <20200522131018.GE11785@e121166-lin.cambridge.arm.com> <7FE3D498-D293-407C-A70C-5E763151477C@flygoat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7FE3D498-D293-407C-A70C-5E763151477C@flygoat.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 22, 2020 at 09:32:10PM +0800, Jiaxun Yang wrote: [...] > >> Is it possible to let this series go into next tree soon? > >> > >> As LS7A dts patch would depend on this series, and I want to > >> make the whole LS7A basic support as a part of 5.8 release. > > > >I think you have all necessary tags to take this in the MIPS > >tree, please let me know if that's the way we want this to go > >upstream - I would not pull MIPS/dts changes into the PCI tree > >and I don't think it is needed for this series. > > Please pull all PCI changes [1~3] into PCI tree. Pulled [1,2,3] into pci/mips, thanks ! Lorenzo