Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp151235imm; Tue, 14 Aug 2018 16:01:35 -0700 (PDT) X-Google-Smtp-Source: AA+uWPz6PI5JMXwbcTjPyWX1M0+CKqawd6WU42JeNfmouPBf7JkqvFav17T0ZQ1yseisOWH1wfTS X-Received: by 2002:a63:d645:: with SMTP id d5-v6mr23440256pgj.450.1534287695073; Tue, 14 Aug 2018 16:01:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534287695; cv=none; d=google.com; s=arc-20160816; b=jNqlnAiJnyk9X//ioFE4britwu+9laUpVDk4IFsYuRLjq591NtlmCi33D+z64Ajdql cf79lqJ1hgjyrcP7F4P0F6ejHXf/HCKvczb0sKveeC+2mOfSVTRcdwA6IopHk6idG7Qr SgEPdW7q0v26N6M/yq17BNrshMgr2IxU8qhQ/VhOlsfDQbEt3FIANWhTxuBV7T6RfovN zXkhpr2uPEuh6OKtPQwLYw+ti1e0XOYkvX2YiQtGCY1vL7G6ZmVMNx6Lpqn/Uf6YiCsM WzAePdmA4WchEy7+V+dDZcjKoJ1Fg6uarqlAOpJHAgJdoZPdYRLYhfZ5SzMX3+sN/AI3 hjPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:references:message-id:date :thread-index:thread-topic:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=sWvShXMxu7aZNTXHp+6mEjQY4JG7PWNMDFF6zpowPQg=; b=b3UTafQ3gDOyWINbR1t4ZMLBvAgdYRK9jrGpGXnoSaPwRk6qRYBEPeNRNFFTsOCMR6 qf3eaAiBuSkv0bN9WnUEnu7JFPtXPmPpozNMCt8WZx3xKX/2kj/OOpXuwQ3MD7ma/bO6 WngvFAgAA70WcIn/AeNB+PpXSJ5wq0rXoZoe2C2ruvu7KMviovbZxeFqLcLp7kinWlhG PJwme+Agb2z7MQ4KCdC1LROiFu5K/QMyoR/kexEZ/l4+1cQvYToMwvctC9ERztkvMGDS FwJwNrAlypQ9tb8pQ9fd3DGDGOIagve53QgqTrqc5U2mEyL3iZfJtHpVemMB6PlEL/8Q pR6g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=OSh534o1; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r3-v6si21084684pgo.606.2018.08.14.16.01.19; Tue, 14 Aug 2018 16:01:35 -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; dkim=pass header.i=@synopsys.com header.s=mail header.b=OSh534o1; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732433AbeHOBtw (ORCPT + 99 others); Tue, 14 Aug 2018 21:49:52 -0400 Received: from us01smtprelay-2.synopsys.com ([198.182.47.9]:60495 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730606AbeHOBtw (ORCPT ); Tue, 14 Aug 2018 21:49:52 -0400 Received: from mailhost.synopsys.com (mailhost3.synopsys.com [10.12.238.238]) by smtprelay.synopsys.com (Postfix) with ESMTP id BD8D024E0BD1; Tue, 14 Aug 2018 16:00:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=synopsys.com; s=mail; t=1534287628; bh=4ICGTsEGSXcmusNDEvuG2KbgASsJhtwMNbSIM+bAc0U=; h=From:To:CC:Subject:Date:References:From; b=OSh534o1mfjE04/qPVNGI/84qB/w5vOx5l2BbuZXlgLk1aYn9AhckOph1oJQN740Z XRs/HheIivC4KLW6ztiAzf1/HcYdiF2XBTo5Gz4qeYgoN4E4/zIFUVTHfsB+mqxlId QYQj6e0KGN3R/0aL2hrC2PusVry18wtGZPwfVP1M8qTzNAv5wJQE3YThsbcY0lA7Y/ 6yKBuz9t7/8isz1ej5yfUYrOSNbYAQN8+cSNrBTUK3sSgXVNgyU2iOI4NRgU0Yjx// PKx0U77QQuhhIbntZWl34CkzCJAbgE1z22tZzKn/CkBisC/wZSQ/WR/Pvn+zjBtx0a eoClEJbwu+mYg== Received: from US01WEHTC3.internal.synopsys.com (us01wehtc3.internal.synopsys.com [10.15.84.232]) by mailhost.synopsys.com (Postfix) with ESMTP id 6DFBC33A0; Tue, 14 Aug 2018 16:00:28 -0700 (PDT) Received: from us01wembx1.internal.synopsys.com ([169.254.1.253]) by US01WEHTC3.internal.synopsys.com ([::1]) with mapi id 14.03.0361.001; Tue, 14 Aug 2018 16:00:28 -0700 From: Vineet Gupta To: Stephen Rothwell CC: Linux-Next Mailing List , "Linux Kernel Mailing List" , Eugeniy Paltsev , Mark Rutland , "Ingo Molnar" Subject: Re: linux-next: manual merge of the arc-current tree with Linus' tree Thread-Topic: linux-next: manual merge of the arc-current tree with Linus' tree Thread-Index: AQHUNBvQfOLwQkVAeEqvzWxvxncsEQ== Date: Tue, 14 Aug 2018 23:00:27 +0000 Message-ID: References: <20180815081141.3f1b1059@canb.auug.org.au> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.144.199.104] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/14/2018 03:11 PM, Stephen Rothwell wrote:=0A= > Hi Vineet,=0A= >=0A= > Today's linux-next merge of the arc-current tree got a conflict in:=0A= >=0A= > arch/arc/include/asm/atomic.h=0A= >=0A= > between commit:=0A= >=0A= > ab0b910490fe ("atomics/arc: Define atomic64_fetch_add_unless()")=0A= >=0A= > from Linus' tree and commit:=0A= >=0A= > 39456148db74 ("ARC: atomic64: fix atomic64_add_unless function")=0A= >=0A= > from the arc-current tree.=0A= >=0A= > I fixed it up (I just used the version from Linus' tree for now) and=0A= > can carry the fix as necessary. This is now fixed as far as linux-next=0A= > is concerned, but any non trivial conflicts should be mentioned to your= =0A= > upstream maintainer when your tree is submitted for merging. You may=0A= > also want to consider cooperating with the maintainer of the conflicting= =0A= > tree to minimise any particularly complex conflicts.=0A= =0A= Thx for the report Stephen. I've dropped my patch for now, let the dust set= tle and=0A= then we can add it.=0A= =0A= Thx,=0A= -Vineet=0A=