Message-ID: <AM6PR06MB4691A5E1603BBE57F35F3B17A6F40@AM6PR06MB4691.eurprd06.prod.outlook.com>
Date:   Tue, 1 Dec 2020 19:48:49 +0000
From:   ZHIZHIKIN Andrey <andrey.zhizhikin@...ca-geosystems.com>
To:     Arnd Bergmann <arnd@...nel.org>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>
CC:     Catalin Marinas <catalin.marinas@....com>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        "linux@...linux.org.uk" <linux@...linux.org.uk>,
        "nicolas.ferre@...rochip.com" <nicolas.ferre@...rochip.com>,
        "ludovic.desroches@...rochip.com" <ludovic.desroches@...rochip.com>,
        "tony@...mide.com" <tony@...mide.com>,
        "mripard@...nel.org" <mripard@...nel.org>,
        "wens@...e.org" <wens@...e.org>,
        "jernej.skrabec@...l.net" <jernej.skrabec@...l.net>,
        "thierry.reding@...il.com" <thierry.reding@...il.com>,
        "jonathanh@...dia.com" <jonathanh@...dia.com>,
        "will@...nel.org" <will@...nel.org>,
        "tsbogend@...ha.franken.de" <tsbogend@...ha.franken.de>,
        "James.Bottomley@...senPartnership.com" 
        <James.Bottomley@...senpartnership.com>,
        "deller@....de" <deller@....de>,
        "mpe@...erman.id.au" <mpe@...erman.id.au>,
        "benh@...nel.crashing.org" <benh@...nel.crashing.org>,
        "paulus@...ba.org" <paulus@...ba.org>,
        "lee.jones@...aro.org" <lee.jones@...aro.org>,
        "sam@...nborg.org" <sam@...nborg.org>,
        "emil.l.velikov@...il.com" <emil.l.velikov@...il.com>,
        "daniel.thompson@...aro.org" <daniel.thompson@...aro.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
        "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
        "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
        "linux-parisc@...r.kernel.org" <linux-parisc@...r.kernel.org>,
        "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
        Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
        arm-soc <arm@...nel.org>
Subject: RE: [PATCH 1/5] ARM: configs: drop unused BACKLIGHT_GENERIC option

Hello Arnd,

> -----Original Message-----
> From: Arnd Bergmann <arnd@...nel.org>
> Sent: Tuesday, December 1, 2020 4:50 PM
> To: Alexandre Belloni <alexandre.belloni@...tlin.com>
> Cc: Catalin Marinas <catalin.marinas@....com>; ZHIZHIKIN Andrey
> <andrey.zhizhikin@...ca-geosystems.com>; Krzysztof Kozlowski
> <krzk@...nel.org>; linux@...linux.org.uk; nicolas.ferre@...rochip.com;
> ludovic.desroches@...rochip.com; tony@...mide.com;
> mripard@...nel.org; wens@...e.org; jernej.skrabec@...l.net;
> thierry.reding@...il.com; jonathanh@...dia.com; will@...nel.org;
> tsbogend@...ha.franken.de; James.Bottomley@...senPartnership.com;
> deller@....de; mpe@...erman.id.au; benh@...nel.crashing.org;
> paulus@...ba.org; lee.jones@...aro.org; sam@...nborg.org;
> emil.l.velikov@...il.com; daniel.thompson@...aro.org; linux-arm-
> kernel@...ts.infradead.org; linux-kernel@...r.kernel.org; linux-
> omap@...r.kernel.org; linux-tegra@...r.kernel.org; linux-
> mips@...r.kernel.org; linux-parisc@...r.kernel.org; linuxppc-
> dev@...ts.ozlabs.org; Arnd Bergmann <arnd@...db.de>; Olof Johansson
> <olof@...om.net>; arm-soc <arm@...nel.org>
> Subject: Re: [PATCH 1/5] ARM: configs: drop unused BACKLIGHT_GENERIC
> option
> 
> 
> On Tue, Dec 1, 2020 at 4:41 PM Alexandre Belloni
> <alexandre.belloni@...tlin.com> wrote:
> > On 01/12/2020 14:40:53+0000, Catalin Marinas wrote:
> > > On Mon, Nov 30, 2020 at 07:50:25PM +0000, ZHIZHIKIN Andrey wrote:
> > > > From Krzysztof Kozlowski <krzk@...nel.org>:
> 
> > > I tried to convince them before, it didn't work. I guess they don't
> > > like to be spammed ;).
> >
> > The first rule of arm-soc is: you do not talk about arm@ and soc@
> 
> I don't mind having the addresses documented better, but it needs to be
> done in a way that avoids having any patch for arch/arm*/boot/dts and
> arch/arm/*/configs Cc:d to soc@...nel.org.
> 
> If anyone has suggestions for how to do that, let me know.

Just as a proposal:
Maybe those addresses should at least be included in the Documentation ("Select the recipients for your patch" section of "Submitting patches"), much like stable@ is. Those who get themselves familiarized with it - would get an idea about which list they would need to include in Cc: for such changes.

That should IMHO partially reduce the traffic on the list since it would not pop-up in the output of get_maintainer.pl, but would at least be documented so contributors can follow the process.

> 
> > > Or rather, SoC-specific patches, even to defconfig, should go
> > > through the specific SoC maintainers. However, there are occasional
> > > defconfig patches which are more generic or affecting multiple SoCs.
> > > I just ignore them as the arm64 defconfig is usually handled by the
> > > arm-soc folk (when I need a defconfig change, I go for
> > > arch/arm64/Kconfig directly ;)).
> >
> > IIRC, the plan was indeed to get defconfig changes through the
> > platform sub-trees. It is also supposed to be how multi_v5 and
> > multi_v7 are handled and they will take care of the merge.
> 
> For cross-platform changes like this one, I'm definitely happy to pick up the
> patch directly from soc@...nel.org, or from mailing list if I know about it.

Should I collect all Ack's and re-send this series including the list "nobody talks about" :), or the series can be picked up as-is?

Your advice would be really welcomed here!

> 
> We usually do the merges for the soc tree in batches and rely on patchwork
> to keep track of what I'm missing, so if Olof and I are just on Cc to a mail, we
> might have forgotten about it by the time we do the next merges.
> 
>       Arnd

Regards,
Andrey

Powered by blists - more mailing lists