Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2201983imu; Fri, 14 Dec 2018 07:20:59 -0800 (PST) X-Google-Smtp-Source: AFSGD/VRnfyxqap9tsGzEnBRRvPQ0o9+4osBQXm0Ze8H4x4xclcZ0OJUgI069Mnt9AJOjGEeIsWC X-Received: by 2002:a63:ae01:: with SMTP id q1mr3000127pgf.402.1544800859042; Fri, 14 Dec 2018 07:20:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544800859; cv=none; d=google.com; s=arc-20160816; b=QtK3f1Zba6oY9aa22ymSC9lORBtMfGJXdHqve0a9sbof548YxuR6q18KQwo65K8NQS QA5orjpMtHvE+7gFd2I7zrXzo/tw7o6vHUvzrDlQl1y5QOvnnSwVawMZ6U1wCzyLB6RP ajc7g93zDtpY1OsK+gFO4GnoIK5cOrgOHLu9sYRzda168CudDVFgod3873YV1QA39RrF +aqTGNuMa/We0dKmXiGkNqQedWxjhlOx1LjTGrtleAYfg0HDsorhHpee1b3v1rVAiOp0 SQneL+aK/7R7Ddb+EAed81zYljZsHo7wyzW5h9V4ItuqwUmdZhPU1TOj65B4OT5xUnBt AtXA== 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; bh=Ux/cp44roeBlT8vmW29rzQZ+r8eNlSJqyBVMu9tPjOU=; b=e3GEG0VsHVuZkRHqZggqmZuXYz2wTSTglY2UsTSftUoVQa7xvytmnNId4ewnHPpqCm OUMQ9IzC6MxjjeCwDCPdAQT0VrF2Q2EWOXTXhDw8teM/bw29IsVom13vyvgZ1XuT2+GK 3GkP1VdD3XRBrAf30cMXaCw1xRemhErJqouoGl86nI0hgn8kJ4NOeZtHYHs0DoDvVoZ/ csu8Uvr7xXXIjYW6j5YE8vXMgD7Xt0JSVxSgUWrgjQA20HEKnb7YOPHvGDJZ74ac7HfT ZZSmk/Nujy/6c5RaSxBXhUAmNSdzyCzYC8o4RvcxN+ZzBG17NPDKTI4fUeM3NMMA+YmH a2qA== 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 o13si4020815pgp.540.2018.12.14.07.20.27; Fri, 14 Dec 2018 07:20:59 -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 S1730425AbeLNPS3 (ORCPT + 99 others); Fri, 14 Dec 2018 10:18:29 -0500 Received: from muru.com ([72.249.23.125]:58400 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730196AbeLNPS3 (ORCPT ); Fri, 14 Dec 2018 10:18:29 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id EF90B80B6; Fri, 14 Dec 2018 15:18:31 +0000 (UTC) Date: Fri, 14 Dec 2018 07:18:25 -0800 From: Tony Lindgren To: Felix Brack Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org, bcousson@baylibre.com, mpfj@newflow.co.uk, mark.rutland@arm.com, robh+dt@kernel.org, linux@armlinux.org.uk, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ARM: dts: am33xx: Remove unnecessary properties Message-ID: <20181214151825.GU6707@atomide.com> References: <20181210132448.7865-1-fb@ltec.ch> <20181211163618.GU6707@atomide.com> <20181211164336.GV6707@atomide.com> <89710fa1-38a9-1628-0651-003332780483@ltec.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <89710fa1-38a9-1628-0651-003332780483@ltec.ch> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Felix Brack [181214 15:12]: > Hi Tony, > > On 11.12.2018 17:43, Tony Lindgren wrote: > > * Tony Lindgren [181211 16:36]: > >> * Felix Brack [181210 05:25]: > >>> Remove the unnecessary properties #address-cells and #size-cells > >>> of node pinmux as there are no child-nodes with property reg. > >> > >> Applying into omap-for-v4.21/dt thanks. > > > > Actually this currently conflicts with the pending > > am33xx l4 ti-sysc changes, so let's wait on this > > one to avoid causing merge conflicts between > > branches. > > > Okay, I see. The changes introduced by my patch would then affect the > new file am33xx-l4.dtsi instead of am33xx.dtsi Yup, and I wanted to keep the am33xx-l4.dtsi in a separate branch from the rest of the dts changes. > > So dropping for now. > > > Will you "apply" my patch once the am33xx l4 ti-sysc changes are applied > or do you expect me to send V2 patch (to be applied to the new > am33xx-l4.dtsi) ? I'd prefer you to send an updated version against Linux next as the am33xx-l4.dtsi changes have been in next for a while now. It is unlikely at this point that they would not get merged, but I'd rather wait a bit before applying to avoid mixing the two otherwise independent branches :) Regards, Tony