Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp361061pxb; Tue, 9 Feb 2021 02:12:11 -0800 (PST) X-Google-Smtp-Source: ABdhPJxmG3/+PD9v42U7qPhZsO2sn3aBRMyBVrcFR6s1aWMcNOl6XZz3PcMJhoHMMuwgFefXijDf X-Received: by 2002:a17:906:854d:: with SMTP id h13mr20723080ejy.124.1612865530848; Tue, 09 Feb 2021 02:12:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612865530; cv=none; d=google.com; s=arc-20160816; b=eiJIA6EgrmV7F+/bhc3pzOQH7MzFbv4azO6o9N4gy5/k08xvIFo/P5Ogw+I1Ykdr69 y5tsS9G+v/IPPGsNiKyUEl/xL3t4zeLNMU8sWG05Kacp8vysjKQvca2by8pxFFAXhVJj N4takObcWgId7zxu7MNo/Jc1cZ/yFGi1iVF240974NBtAovvfrqQsmjTgqEQ4goxIKou QLE2jvWwSZb+7IvfnMoxcHJD7Y0IVnbwqXEuy04bqj58ceH1tjK25FZaikcvYCs44CpR LNfisJO3StkQ595/Jyt/CAhmTbb24szxy+DEi5MD1wx+rgcdXFsGTUcaee6xv2jhjDVb 3WTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=bKhdVSr9a9o5NhirinVW6rRyQV4KNd1sg3w4d1Klbwc=; b=QfpDwacbeDh3DJ65noVI+pPwT2gQcQ01hNtJwPuV0atJwdSa6djbpb0317ZThJ/gOt EKM0ZVtn+Ozq7Lhnryotj8jDUv0Ra/MAQ3cx30D/mffDJbSlzDPTlmFhy5KYWQyeF47K Sa5I5Fn9mYfsfys+1L5P2v9A7ETRX8ZeKa1x0eeC3sEiKANWri8yoghIXw0LbgG+o6Ti rCtu1Rq+zOeDP2iAbItqK3sF6QBTfPzOYY16Pyc1Af+nYUvX7cBDVAjuiCtujftbd9TC 0GTgnH4N4zPjnfH1wmv/nAZW4jHU02UJ7svcY7Tjp5BkDAfRFaYBBTpiZRF7yfFNGw1m L5Rg== 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 ce8si13076647ejb.146.2021.02.09.02.11.47; Tue, 09 Feb 2021 02:12:10 -0800 (PST) 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 S231446AbhBIKKn (ORCPT + 99 others); Tue, 9 Feb 2021 05:10:43 -0500 Received: from mail-ot1-f45.google.com ([209.85.210.45]:33636 "EHLO mail-ot1-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231265AbhBIKCN (ORCPT ); Tue, 9 Feb 2021 05:02:13 -0500 Received: by mail-ot1-f45.google.com with SMTP id 63so16978299oty.0; Tue, 09 Feb 2021 02:01:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bKhdVSr9a9o5NhirinVW6rRyQV4KNd1sg3w4d1Klbwc=; b=fX0lB+pImKJE6n1Oq5/v19cZLXfhiUIsAXn7rz94IyGCUv+EukpOhphxxqH4piQbvo /ABJs/AM4UGRV7XxMg/iyyjXdbq90/YUAqpnk2hgUxVKs477+bbAtztpbAuyfHQnLDCY tj2k6QvcbfWdq07lq6HykJDnqaHGnQm5tXhDKgwyyEncROyqGlRoVZEK/MUfwW57HSYW 2e6YuYgc8HwJ6jVqrTJPLSkzy2ekKONZAJTAvLrZJaVjD/leo76bvVt0iAkX1YWDQrYC WZR48UfcSrkh0AZq/EsJltQJrlOivswY0wXsAv/ZL5BayN4PsvFFnAO16ZKFQSho8sXD zAZA== X-Gm-Message-State: AOAM530u6LwASN4TvDWb3x70v6GWXxxr9rk+0Hb9oAraiEFxknkT9lWD ahKi1YUjFjtQzqHYJ3Xj18T8ppOmi+0N98ZLxDA= X-Received: by 2002:a9d:3604:: with SMTP id w4mr15553100otb.107.1612864885239; Tue, 09 Feb 2021 02:01:25 -0800 (PST) MIME-Version: 1.0 References: <20210128170331.4f2ac87b@canb.auug.org.au> In-Reply-To: <20210128170331.4f2ac87b@canb.auug.org.au> From: Geert Uytterhoeven Date: Tue, 9 Feb 2021 11:01:14 +0100 Message-ID: Subject: Re: linux-next: manual merge of the gpio-brgl tree with the arm-soc tree To: Stephen Rothwell Cc: Bartosz Golaszewski , Olof Johansson , Arnd Bergmann , ARM , Bartosz Golaszewski , Linux Kernel Mailing List , Linux Next Mailing List , Nobuhiro Iwamatsu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 28, 2021 at 7:05 AM Stephen Rothwell wrote: > Today's linux-next merge of the gpio-brgl tree got a conflict in: > > arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > between commit: > > 4fd18fc38757 ("arm64: dts: visconti: Add watchdog support for TMPV7708 SoC") > > from the arm-soc tree and commit: > > 08bc3941b6a4 ("arm: dts: visconti: Add DT support for Toshiba Visconti5 GPIO driver") > > from the gpio-brgl 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 arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > index 37da418393e0,950010a290f0..000000000000 > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > @@@ -42,7 -42,6 +42,11 @@@ > clock-names = "apb_pclk"; > }; > > +&wdt { > + status = "okay"; > + clocks = <&wdt_clk>; > +}; > ++ > + &gpio { > + status = "okay"; > + }; Probably some sort order should be taken into account (gpio before uart0), also avoidng the conflict? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds