Received: by 10.223.164.202 with SMTP id h10csp3048448wrb; Mon, 13 Nov 2017 01:16:43 -0800 (PST) X-Google-Smtp-Source: AGs4zMaAY621aRRdiInjche6U2nE7irdlGYI/gu40yJ0WhN0GBR5DJc8aC/epfIvDEWvfDWtTj+X X-Received: by 10.99.110.3 with SMTP id j3mr8110834pgc.70.1510564603360; Mon, 13 Nov 2017 01:16:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510564603; cv=none; d=google.com; s=arc-20160816; b=c1MNyxwo2VaQCKC7hwpZ9gUHkfLj/f09y9pS5H4lV3hshPZBlOTquxPy0wfFBotB4O xRGdsFGgpyjcz3S29l8gpHbz+AGLjH2iSoxYNCxrkZeRrLGuwmuLYA7ZqUzhzl1nu6KF ghlKjM+kv8guAvrDJJEPRDQzqVSaRwfG3iyDsERCEvRGXz6WWxfbUNRWbfMliH80hf8l GNM+SlqPeUXGnc6rtYui1iGxutH0zlpGA3PhAXHjQpXzeK9Bma/DwIgm8snhR1TUo0Jn 7BItXl5eE3yJVy6KxzB2jZ3ykB32ImFzFBofMTzyjaMMCRNuwUUZGMEHwijtVmSkTSRw ebmQ== 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=Ywg0PZ38T5v+9cbpd94T9XhefpxOt7INoRufC0sW/Qs=; b=qOVZNAlZoQYAEEcc9smQnFvjTFYr8zc15S0gWNsbHGhU04fVJkDRjHdDojmvj397Bb md5GHp3PBm2YEC8GJZOQWefqws1cBfK3LT+yr9kPuRMSayKy1MBJHgkkhD33qLTexZSl Al68/YFDwn6PthQTPkWoBlvYACDaXNpRNAL3NNmTw/NQVa9ZYwK7B95YDQksTkapXAYk kuhQq9LkpdsLinPaUklYcDqab94y95U6gBWuWTV6NyAeuBS5tVFjFPIG6Pm33Fmv/SNX 90QeXI9Hg8VAc5FXIGQoSSLxxmmPD72Fw/x2k2Y8dh5Dc9fH5BU74maWX4RXAJjinHEh ODcg== 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 k7si752306pls.500.2017.11.13.01.16.30; Mon, 13 Nov 2017 01:16:43 -0800 (PST) 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 S1752168AbdKMJPO (ORCPT + 92 others); Mon, 13 Nov 2017 04:15:14 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:43722 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554AbdKMJPM (ORCPT ); Mon, 13 Nov 2017 04:15:12 -0500 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 13D7E1435; Mon, 13 Nov 2017 01:15:12 -0800 (PST) Received: from armageddon.cambridge.arm.com (armageddon.cambridge.arm.com [10.1.206.84]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 008153F246; Mon, 13 Nov 2017 01:15:10 -0800 (PST) Date: Mon, 13 Nov 2017 09:15:08 +0000 From: Catalin Marinas To: Stephen Rothwell Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Lorenzo Pieralisi , Will Deacon Subject: Re: linux-next: manual merge of the arm64 tree with Linus' tree Message-ID: <20171113091507.fctbn7xtykyd6zvz@armageddon.cambridge.arm.com> References: <20171101075723.20965225@canb.auug.org.au> <20171113170953.0cdda59d@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171113170953.0cdda59d@canb.auug.org.au> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Mon, Nov 13, 2017 at 05:09:53PM +1100, Stephen Rothwell wrote: > On Wed, 1 Nov 2017 07:57:23 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the arm64 tree got a conflict in: > > > > drivers/acpi/arm64/iort.c > > > > between commit: > > > > 37f6b42e9c29 ("ACPI/IORT: Fix PCI ACS enablement") > > > > from Linus' tree and commit: > > > > 896dd2c32484 ("ACPI/IORT: Make platform devices initialization code SMMU agnostic") > > > > from the arm64 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. [...] > > diff --cc drivers/acpi/arm64/iort.c > > index de56394dd161,7dc964f4d8f1..000000000000 > > --- a/drivers/acpi/arm64/iort.c > > +++ b/drivers/acpi/arm64/iort.c > > @@@ -1215,7 -1326,7 +1357,8 @@@ static void __init iort_init_platform_d > > struct acpi_table_iort *iort; > > struct fwnode_handle *fwnode; > > int i, ret; > > + bool acs_enabled = false; > > + const struct iort_dev_config *ops; > > > > /* > > * iort_table and iort both point to the start of IORT table, but > > @@@ -1235,12 -1346,8 +1378,11 @@@ > > return; > > } > > > > + if (!acs_enabled) > > + acs_enabled = iort_enable_acs(iort_node); > > + > > - if ((iort_node->type == ACPI_IORT_NODE_SMMU) || > > - (iort_node->type == ACPI_IORT_NODE_SMMU_V3)) { > > - > > + ops = iort_get_dev_cfg(iort_node); > > + if (ops) { > > fwnode = acpi_alloc_fwnode_static(); > > if (!fwnode) > > return; > > Just a reminder that this conflict still exists. Thanks for the reminder. Will (cc'ed) is handling this merging window and AFAIK the pull request will go with this conflict unsolved (to avoid a back merge from a newer Linus tree commit). -- Catalin From 1583930090601609436@xxx Mon Nov 13 06:10:46 +0000 2017 X-GM-THRID: 1582808208574620566 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread