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

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

On Thu, Nov 09, 2023 at 10:51:12AM -0500, Steven Rostedt wrote:
> On Thu, 9 Nov 2023 11:32:16 +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.
> 
> You usually just send fixes, which is fine for not Cc'ing LKML.
> 
> Please do not strip linux-trace-kernel, though. As it keeps the responses
> in patchwork.
> 
> > 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).
> 
> Which is fine.
> 
> I'm care more about new features, as tracing / scheduling / etc affect the
> entire kernel. Changes in DRM usually only affect DRM. But a scheduling or
> tracing change, could affect DRM, which is why I want to keep those patches
> going to the generic mailing list.

They won't be seen by most DRM people though, as those people are most
likely not following LKML due to the amount of e-mails. I barely even
ever read lists these days due to the mail volume, even for the
subsystems I'm most involved with :-S

-- 
Regards,

Laurent Pinchart