[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6dafde7d-17c6-bd25-dbe8-7f7acf80fd91@gmail.com>
Date: Tue, 29 Mar 2022 12:06:38 +0200
From: Matthias Brugger <matthias.bgg@...il.com>
To: Tony Lindgren <tony@...mide.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Daniel Palmer <daniel@...f.com>,
Ansuel Smith <ansuelsmth@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
DTML <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-actions@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
"open list:TI ETHERNET SWITCH DRIVER (CPSW)"
<linux-omap@...r.kernel.org>,
"open list:ARM/Amlogic Meson..." <linux-amlogic@...ts.infradead.org>,
linux-arm-kernel@...s.com, linux-aspeed@...ts.ozlabs.org,
linux-rpi-kernel <linux-rpi-kernel@...ts.infradead.org>,
chrome-platform@...ts.linux.dev,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
linux-stm32@...md-mailman.stormreply.com,
kernel@...electronics.com, linux-mediatek@...ts.infradead.org,
openbmc@...ts.ozlabs.org,
linux-tegra <linux-tegra@...r.kernel.org>, linux-oxnas@...ups.io,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
linux-unisoc@...ts.infradead.org,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
linux-realtek-soc@...ts.infradead.org
Subject: Re: [RFC PATCH 0/1] Categorize ARM dts directory
On 29/03/2022 11:54, Tony Lindgren wrote:
> * Geert Uytterhoeven <geert@...ux-m68k.org> [220329 09:02]:
>> On Tue, Mar 29, 2022 at 10:03 AM Tony Lindgren <tony@...mide.com> wrote:
>>> 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 :)
>>
>> Git merge/rebase/cherry-pick should handle renames fine?
>
> Possibly.. Not sure I'd count on that based on my earlier experiences
> though :)
>
Yes. If this could be split up in per silicon-vendor patches, the maintainer
could take them. Although it might be a pain to soc maintainers to resolve small
conflicts when merging that branches.
Just my 5 cents.
Matthias
Powered by blists - more mailing lists