Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp2643555imm; Fri, 20 Jul 2018 02:14:44 -0700 (PDT) X-Google-Smtp-Source: AAOMgpeBZQCQewgqCBsrzcabVE9A1/KmoITonQ4TyOSycQyGy7rb196HXOQ4+/GwNCbIWhh6oqE1 X-Received: by 2002:a63:89c7:: with SMTP id v190-v6mr1275513pgd.194.1532078084690; Fri, 20 Jul 2018 02:14:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532078084; cv=none; d=google.com; s=arc-20160816; b=OF67QJVA3AobtUXTcZTuuEuRTEGVxejBD7DPWxoH2EYTMcLvVEorMTw46vl9diJoAV 5UNqK60dwjJ3pWiQQawp+6OOC8xMer3LjRzKPSauAFvhQpUPluLQ9NqAyD7iN3He2Koj In8LhRuWBGpyfqlVq1gVDJfvw4Lod0ZPOoHj0d7SyNGTtu9I+T9CzGXj1K2SYo6Ty3kq sF2ZSQHnQgsQPXktggwmEE6flGe2TgaeW62uvon/1/sAnEFq0ZHP1RdwTsutvBLWAJko bxhp6DZQEsnI9w7/dfGbMPpGEaMKwOoMkgzHNZyUYXKoeCy1gNaObCQETZUiAHd5n+bk XFsg== 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:arc-authentication-results; bh=PxthokuyRB5vN4QSA9i4V7L8C/Vhef5T9aYUKtAF1os=; b=UYJWuxj1p7KuJ9TaOhkw5Z7ZjeAfNCJxNnXMNSX9xXQHEbX1ufrhxDDokt4YzrFgwt hr5WkXJzt+CJcl1K9H1hTHX8Z1cw1Vhhkh7CGN6vwC3M6An6hBdaKDg4Mvf8FLZzx8TB 8mLG59BhvapVzZWWEMDZQ4xCDIPpD8u/GqO+RC9qZxLHWWvZ9rEN+SzueFQuPMgpBgc2 cKLdp5ahpM0xs49I7ondKlMlHfn8z2IKj2R66rj648lx62YQu2O+YCDpE8Xn4PSI8kRs 5Blq+FAIBcoHiFM+xlCmw4+HBTYcIMyZ/2oQ/pyHiphIkoaJ8D/rwQUET0Jhabhjta/7 ep+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i4-v6si1362387pgl.435.2018.07.20.02.14.29; Fri, 20 Jul 2018 02:14:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727671AbeGTKBN (ORCPT + 99 others); Fri, 20 Jul 2018 06:01:13 -0400 Received: from foss.arm.com ([217.140.101.70]:59976 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727179AbeGTKBN (ORCPT ); Fri, 20 Jul 2018 06:01:13 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 67F3580D; Fri, 20 Jul 2018 02:13:54 -0700 (PDT) Received: from red-moon (red-moon.cambridge.arm.com [10.1.206.55]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 119A03F5B3; Fri, 20 Jul 2018 02:13:52 -0700 (PDT) Date: Fri, 20 Jul 2018 10:15:53 +0100 From: Lorenzo Pieralisi To: Stephen Rothwell Cc: Bjorn Helgaas , Linux-Next Mailing List , Linux Kernel Mailing List , Sergei Shtylyov , Evan Wang , Thomas Petazzoni Subject: Re: linux-next: manual merge of the pci tree with Linus' tree Message-ID: <20180720091553.GA23214@red-moon> References: <20180720110310.6d07e86e@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180720110310.6d07e86e@canb.auug.org.au> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 20, 2018 at 11:03:10AM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the pci tree got a conflict in: > > drivers/pci/controller/pci-aardvark.c > > between commit: > > 1df3e5b3feeb ("PCI: aardvark: Fix I/O space page leak") > > from Linus' tree and commit: > > 6df6ba974a55 ("PCI: aardvark: Remove PCIe outbound window configuration") > > from the pci tree. > > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is submitted for merging. You may also want to consider cooperating > with the maintainer of the conflicting tree to minimise any particularly > complex conflicts. > > -- > Cheers, > Stephen Rothwell > > diff --cc drivers/pci/controller/pci-aardvark.c > index 0fae816fba39,d5030cd06197..000000000000 > --- a/drivers/pci/controller/pci-aardvark.c > +++ b/drivers/pci/controller/pci-aardvark.c > @@@ -843,13 -809,7 +809,7 @@@ static int advk_pcie_parse_request_of_p > > switch (resource_type(res)) { > case IORESOURCE_IO: > - advk_pcie_set_ob_win(pcie, 1, > - upper_32_bits(res->start), > - lower_32_bits(res->start), > - 0, 0xF8000000, 0, > - lower_32_bits(res->start), > - OB_PCIE_IO); > - err = pci_remap_iospace(res, iobase); > + err = devm_pci_remap_iospace(dev, res, iobase); > if (err) { > dev_warn(dev, "error %d: failed to map resource %pR\n", > err, res); Hi Stephen, thanks for fixing this up, the fix looks fine to me (Thomas please confirm), if it is I would ask Bjorn please to send it upstream when the time for the PCI pull request comes. Thanks, Lorenzo