Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp254262pxb; Tue, 29 Mar 2022 03:34:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx1eoDQYdYy8VkS7lHWn/SEDthwSK6D8QP/Cq9asyYTTplKJn9ZGEf4bVkHrXsp6pjud1ji X-Received: by 2002:a17:907:8a25:b0:6d7:d59:6912 with SMTP id sc37-20020a1709078a2500b006d70d596912mr33525678ejc.259.1648550094411; Tue, 29 Mar 2022 03:34:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648550094; cv=none; d=google.com; s=arc-20160816; b=oTE7k9KWEU6USqz9UkPPtdDlfIZVZIce0ejn7ju9S1rcXkuX+ZYwrWjsCMLiDqOKfB VHHkKG6MudSTBwVZYwt5CY3BvS5S2FapI2nf2+PbkDYyRPxoKOERtfQQIooY4Ybw+fbd nQIg25ci5kSZNfhIPSSqZcJPmevaKWt3qdVIc6BTp6+NXt1NYwobRCKVG2JwnfqmmXhX AhUzaAUi8qaDP2yiy9jTNsDnyP5UmWZynaHyy8TTAPgSYPluowvIvR/r9vxYiypd+roS CM46XBi/6PMMiV6QJ2DgWx37RhObaD6H4o49RnZMNSXacOY3HUw3f/k1XVKHXMl7N9pB XqWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:cc:to:from:date:references:in-reply-to :message-id:mime-version:user-agent:dkim-signature:dkim-signature; bh=g+MRVCTHkd5UITx1/MCA0rtdiS/Q7gdlkLwbx1Cvlxo=; b=XTZUbtNmwMLqw+51Lmj/03WgweBZsZSv5Oov79BkdqIeFIPTcRtTTDJ0810tATRuf2 7XxooVFsdutzj58EzD4LHD1L0IPtqz4ijy0Ur73p4Xrz9Xa6eZcr4oqGsr2zJUpVHV3w idsiAWUvua4Iq3u1OfH+s3qGVaLPjR7oJmmGMjHIxlxd5zIxggYPu+lUL8aSX7HeBBT1 qSl9BMiMcjZhI4AdCLeXNZDKEdaLRxl5yUUz5zcHE8C7VkJU2lwT96UjXlRfcyt3tLDq ooFkGakHPL2Bb+wL5bRsnU0O++/SlnrLSwO9KyUxxltyEjKittCkRg1TvaT/rg6LodOI QNwQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm3 header.b=UCo5xVnv; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=JQKycoTg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id dx26-20020a170906a85a00b006e00c59f3a6si9568987ejb.921.2022.03.29.03.34.06; Tue, 29 Mar 2022 03:34:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm3 header.b=UCo5xVnv; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=JQKycoTg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234002AbiC2IeQ (ORCPT + 99 others); Tue, 29 Mar 2022 04:34:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51848 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233989AbiC2IeN (ORCPT ); Tue, 29 Mar 2022 04:34:13 -0400 Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 073D6EF0A5; Tue, 29 Mar 2022 01:32:28 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id C8AFC580117; Tue, 29 Mar 2022 04:32:25 -0400 (EDT) Received: from imap49 ([10.202.2.99]) by compute5.internal (MEProxy); Tue, 29 Mar 2022 04:32:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; bh=g+MRVCTHkd5UITx1/MCA0rtdiS/Q7gdlkLwbx1 Cvlxo=; b=UCo5xVnvSc2K5kqHRzTJYLeCTDsbjgl6xT1NBykQQVKMp4Ur92CcFO AVM/JayZKVAC/L65NLtrgIbuEHLVwP1Co3xz7FvhPeYlG1Aa5OHK5Qzj2LLMcBlE WDtU+9q9xR4065u7bzMG2cnDmDNge9YR3DUCJyjxKPy6ijNuBxr2WhIiWtmAFGLx CaVwyLl64hj1MiG3Uig1TLYu4vrIGHosrlS82ja6VAHEBoC5JYmZ2CKUWQMpqg+p LhX0oBQIe2SVGDKB1tl9YuLNvxELH4cOL2WMDEfBEJeyYF2z/QfC0sM0WfFEA9jv yiENlM4gRwAggRNn+gcXyaRjlMVLYwRQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=g+MRVCTHkd5UITx1/ MCA0rtdiS/Q7gdlkLwbx1Cvlxo=; b=JQKycoTgRna0MzP3EC2Bm6lralytF7Tvt lO0V5VJRByINopZ+fWpwTMDpmc9b/kA60ODT10jjyv7RLyd3OIx56kYmaRKvKXC+ 9qywkBjHLtg84fuHVkJ82sdvyWSVvO7j8dRzTPrBA5cWRk2mWM6v+O/RybVFk6XN 1317aXIiz7LSlCY9H/UvNDXEnOEWcl2X8I5I9ZMOO6mUX7BmtuqNX/TOlTncnjxM vnb/YbOBUfwse4qT7wmShdeh7Zr9gvKg4veBUWBzDumgWjl4uoEolDtlj0LQms3L KmnJxQzF1LHoY56R0OmEIx4KCtCggE0RHmifBELWQFRqbXe/dRoUQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudehledgtddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdetnhgu rhgvficulfgvfhhfvghrhidfuceorghnughrvgifsegrjhdrihgurdgruheqnecuggftrf grthhtvghrnhephefhfeekgfekudevheffheeihedujeefjeevjeefudfgfeeutdeuvdeh hfevueffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh eprghnughrvgifsegrjhdrihgurdgruh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 599DFF6043F; Tue, 29 Mar 2022 04:32:24 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-4911-g925b585eab-fm-20220323.003-g925b585e Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20220328000915.15041-1-ansuelsmth@gmail.com> Date: Tue, 29 Mar 2022 19:02:04 +1030 From: "Andrew Jeffery" To: "Tony Lindgren" , "Daniel Palmer" Cc: "Ansuel Smith" , "Rob Herring" , "Krzysztof Kozlowski" , linux-arm-kernel , DTML , "Linux Kernel Mailing List" , linux-actions@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-omap@vger.kernel.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@axis.com, linux-aspeed@lists.ozlabs.org, linux-rpi-kernel@lists.infradead.org, chrome-platform@lists.linux.dev, linux-renesas-soc@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, kernel@dh-electronics.com, linux-mediatek@lists.infradead.org, openbmc@lists.ozlabs.org, linux-tegra@vger.kernel.org, linux-oxnas@groups.io, linux-arm-msm@vger.kernel.org, linux-unisoc@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-realtek-soc@lists.infradead.org Subject: Re: [RFC PATCH 0/1] Categorize ARM dts directory Content-Type: text/plain X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE,WEIRD_QUOTING autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 29 Mar 2022, at 18:23, Tony Lindgren wrote: > Hi, > > * Daniel Palmer [220328 08:53]: >> Hi Ansuel >> >> On Mon, 28 Mar 2022 at 09:09, Ansuel Smith wrote: >> > >> > Hi, >> > as the title say, the intention of this ""series"" is to finally categorize >> > the ARM dts directory in subdirectory for each oem. >> >> While I agree with this change and think it's for the good (browsing >> the ARM dts directory at the moment is frustrating..) I think >> buildroot and others need to be told about this as it'll potentially >> break their kernel build scripting for ARM and probably messes up the >> configs they have for existing boards. > > Yeah.. And ideally this would be done in smaller steps as these will > conflict with all the other pending patches. > > For example, I have a pile of pending omap clock clean-up dts patches > posted and tested waiting for v5.19-rc1 to apply. I'd rather not start > redoing or fixing up the patches with sed :) > > What I'd like to have see is that at some point when suitable we move > one machine at a time with a script if possible.. Maybe the dtb files > generated would need to remain in the current directory until all of > the machine dts files are moved? That should help with the build > scripting too probably :) There's probably some reason not to, but could we symlink the new paths in the subdirectories to the existing files to handle the transition? Then do the move to remove the symlinks at some future point. Andrew