Re: [workflows]RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org

Alex Elder
2023-11-09T17:14:41Z

On 11/9/23 3:27 AM, Laurent Pinchart wrote:
> On Thu, Nov 09, 2023 at 11:32:16AM +0300, Dan Carpenter wrote:
>> On Wed, Nov 08, 2023 at 02:04:15PM -0500, Steven Rostedt wrote:
>>>
>>> Right. For example, I use linux-trace-kernel@ to add patches to patchwork,
>>> but I prefer the discussions to be done on LKML.
>>
>> I had no idea that how tracing worked... I normally strip out mailing
>> lists from my patches if I think they're not necessary so I seldom CC
>> lkml. In years past, there used to be a lot of complaining about CC'ing
>> too many people so I try to trim the CC list when I send patches.

I used to do this too but at some point I was told I was leaving
someone or some list out. It seemed get_maintainer.pl was returning
a smaller list of addressees than it once did, so I just started using
the list it produces. It seems excessive though.

My input is that whatever the outcome of all this discussion, please
define it as policy and have get_maintainer.pl implement it. I don't
want to have to think too hard about who *should* be included (beyond
people I already know).

-Alex

>
> I do exactly the same and drop LKML from most of my patch submissions if
> there are more "appropriate" (in the sense of more targetted) lists
> reported by get_maintainer.pl.
>
>> Networking doesn't need to be CC'd about wireless patches.
>> Drm doesn't need to be CC'd about amd gpu driver patches.
>>
>> And for bug reports, I only ever CC one lore mailing list. (For zero
>> day bot stuff, the bot chooses the CC lists).
>