Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3843409pxj; Tue, 15 Jun 2021 09:48:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzyLNW1F2WpNmoLIOwfJb/1Wfa8VGwSI0IrBDFG55odI0/qydBq1cROVD2iXvG4U/L9ZX/v X-Received: by 2002:a05:6e02:13a9:: with SMTP id h9mr320959ilo.96.1623775690817; Tue, 15 Jun 2021 09:48:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623775690; cv=none; d=google.com; s=arc-20160816; b=U1+SHpcgtW0uV8hKKikJEjk3nRK6FvXZQAhRJy8SSUC0qXgKGOrqsnpRGBFv3vztL9 z36Bcju38DM7ulhZ1lFs/qThbNqw/uSTYeJyUXL1DrLK/uzEiO0OIV4VlJCn9zQDvjKn 7oi7+dEOKNKDmejP5yuLC0JlgXYJl5cBUdzZP8ZdQQaXzg+f9TiMXm9Oy8rIg6EeRMSD LKMFl26Oz7eeUhXpZi46Yyg75xoH/RKHYerKGstkSm1yQLA74v5WIzJidqMUikt7KwMD 86HNP1Sm9wAFG7ld0QBvfNqQb9+ComRdfl5oi9s1HfHaYHJN3S7S8FJlNvlG8c0WPhzF eyzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=soZuNKhY6jgWtCwVDEm/wkIUtEwcQeIpydTpwrVHeYI=; b=lzjorN+2k/oMS5ArzxKQkilX6h66WkUjVVHOW/5joCSHbJUOBCHwE2LpxPmZtmhpXL 31D8j/UbYXDalpZMM7jABbafXK0UWr5y/TcyyHjBXFKgC7QSU8RGmctSrtl0GooyR8y6 32HD+JIGmh4w7ZDdYvs1NnNuI//8Y3OSUuJwZE3Fkpr5ldEspojUL/KgNLdqcdIlOVsH pxI/kQTS2q46xUodymfwzaDaOxU5KbPSaBQnlcEOff4wB7bPOqngpfSJgQUXG5nuNT2T Z0m8v343qPGxNZ8A5l2rOAcQjN0TqvnvXm10fq7zhV45iIAlmgf6mYfnAEtDiCBfYNNk hoIA== 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 j12si8087357ils.44.2021.06.15.09.47.58; Tue, 15 Jun 2021 09:48:10 -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 S231301AbhFOQtN convert rfc822-to-8bit (ORCPT + 99 others); Tue, 15 Jun 2021 12:49:13 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:52109 "EHLO relay12.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230254AbhFOQtN (ORCPT ); Tue, 15 Jun 2021 12:49:13 -0400 Received: (Authenticated sender: miquel.raynal@bootlin.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 25CBA200009; Tue, 15 Jun 2021 16:47:05 +0000 (UTC) Date: Tue, 15 Jun 2021 18:47:04 +0200 From: Miquel Raynal To: Stephen Rothwell Cc: Rob Herring , Richard Weinberger , Linux Kernel Mailing List , Linux Next Mailing List , Rob Herring , Vignesh Raghavendra Subject: Re: linux-next: manual merge of the devicetree tree with the mtd tree Message-ID: <20210615184704.4204347f@xps13> In-Reply-To: <20210615125958.541c275c@canb.auug.org.au> References: <20210615125958.541c275c@canb.auug.org.au> Organization: Bootlin X-Mailer: Claws Mail 3.17.7 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, Stephen Rothwell wrote on Tue, 15 Jun 2021 12:59:58 +1000: > Hi all, > > Today's linux-next merge of the devicetree tree got a conflict in: > > Documentation/devicetree/bindings/mtd/ti,am654-hbmc.txt > > between commit: > > 6947ad674944 ("dt-bindings: mtd: Convert ti, am654-hbmc.txt to YAML schema") > > from the mtd tree and commit: > > 9b358af7c818 ("dt-bindings: mux: Convert mux controller bindings to schema") > > from the devicetree tree. > > I fixed it up (the latter removed the file, so I just did that) 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. > Thanks for the warning. Indeed the txt file being touched by 9b358af7c818 is being updated into a yaml file which does not reference the mux binding anymore. Rob, how do you want to proceed? Thanks, Miquèl