Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp269605yba; Thu, 18 Apr 2019 00:37:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqwFrHpYcYskP2n9QAzFdJfdO+75eVV6PWvAdIebSb0iP17mD5PyVgKyOq8fMAlkXW8Q3Hld X-Received: by 2002:a17:902:7883:: with SMTP id q3mr94081007pll.60.1555573022159; Thu, 18 Apr 2019 00:37:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555573022; cv=none; d=google.com; s=arc-20160816; b=S4hQHnfbvgdQwlB4TFpO/eUtHOUBSwEdRJxVgwlCND4i+bHRxfQTLOJ/gEc/n43sjr DO5CZNYa1Ni6RO6NtGSiKH+AhVX3OLAM03O6QjtamDqd5DTsty1psSgGvOhu4nNKtT9U RhWWX686nzPhPFtzWMI2zzFtrEIuKQR6NsMoPCi82tnirhHOkAH8FDStklFltO9KTc9k ZBQ+cqjF1N79BR1uzo4O/i5DS4Iri/lp4WXYw7T5SI6zm4R7eIpXBNVxhGy9zU/AUIpN +OmLoqv86ZK2dctJIp7HjiCveaFH2oTxWD1evwZh8dluoE+2OmAJCiQ10rk1CAvRBlNc xQDA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=9/Gmr7oaA1RFGWSo/FnqvxMUE7l5Gjg0kl8F+F95zNM=; b=tHAGQSu+v+WGKKaOpHofzfhQ2dZhcF828AyY/MvBIfQCLlTouY1leB497IIfxdkJ0U EVM9+NaE9+6s6Ru8ZS/8iieMz/NfezFTYwNrx9JO1CZMEzWqU5oRynHtUTw6j6Ai+kUO FyXljZXYGPiv0RICUaqv+cv2bNQ0RDWagZqrmaTlwcNvXEFgwJnub57j3hs3GDw3psE5 7LrgoJqdd43Eyyxx3S3qhMapr3OswY+hlDFfkpXPDiuQPX/qC8b7Ed0WcUcn1MiLu+RC QMpPGpfxAlFCcbuNPXBArZEmpgZWfQBriE+ld15pU2j3egBqxpz7tIldgo8zWnt4RuKm 3/KQ== 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 d186si1612370pfa.218.2019.04.18.00.36.47; Thu, 18 Apr 2019 00:37:02 -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 S2388172AbfDRHfq (ORCPT + 99 others); Thu, 18 Apr 2019 03:35:46 -0400 Received: from ns.iliad.fr ([212.27.33.1]:50628 "EHLO ns.iliad.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729446AbfDRHfq (ORCPT ); Thu, 18 Apr 2019 03:35:46 -0400 Received: from ns.iliad.fr (localhost [127.0.0.1]) by ns.iliad.fr (Postfix) with ESMTP id 9A9E120140; Thu, 18 Apr 2019 09:35:44 +0200 (CEST) Received: from [192.168.108.49] (freebox.vlq16.iliad.fr [213.36.7.13]) by ns.iliad.fr (Postfix) with ESMTP id 7E3A8200C9; Thu, 18 Apr 2019 09:35:44 +0200 (CEST) Subject: Re: linux-next: manual merge of the phy-next tree with the qcom tree To: Stephen Rothwell , Kishon Vijay Abraham I , Andy Gross Cc: Linux Next , LKML , Bjorn Andersson , Jeffrey Hugo References: <20190418152954.255015e1@canb.auug.org.au> From: Marc Gonzalez Message-ID: Date: Thu, 18 Apr 2019 09:35:44 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190418152954.255015e1@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP ; ns.iliad.fr ; Thu Apr 18 09:35:44 2019 +0200 (CEST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18/04/2019 07:29, Stephen Rothwell wrote: > Today's linux-next merge of the phy-next tree got a conflict in: > > Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt > > between commit: > > 369b89366a3d ("dt-bindings: phy-qcom-qmp: Tweak qcom,msm8998-qmp-ufs-phy") > > from the qcom tree and commit: > > 2815588ea64b ("dt-bindings: phy-qcom-qmp: Add qcom,msm8998-qmp-pcie-phy") > > from the phy-next 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. Hello Stephen, The current state of Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt is indeed: For "qcom,msm8998-qmp-usb3-phy" must contain "phy", "common". For "qcom,msm8998-qmp-ufs-phy": must contain: "ufsphy". For "qcom,msm8998-qmp-pcie-phy" must contain: "phy", "common". For "qcom,sdm845-qmp-usb3-phy" must contain: "phy", "common". It is not clear to me what I could/should have done differently to avoid the conflict? Regards.