Re: RFC: Github PR bot questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Thu, Jun 17, 2021 at 05:24:50PM +0200, Mauro Carvalho Chehab wrote:
> > > A change like that would touch lots of subsystems, making
> > > to spend a lot of time processing it, and producing thousands of
> > > entries (btw, we had a change somewhat similar to the above a long time
> > > ago when mutex API was introduced and most of the semaphores were converted
> > > to use mutex kAPI instead).  
> > 
> > What I end up doing in those cases is only Cc'ing the subsystem
> > maintainers. But that's a manual step of dropping all the driver and
> > SoC maintainers.
> Yeah, surely it would be a lot better if the maintainer's file would
> have a way to distinguish between driver and subsystem maintainers.

Well, the problem here is really that get_mainters is broken and things
anyone touching a file would care about future patches.  Right now the
only workaround for that is to get yourself added to

The actual MAINTAINERS file processing issues are minor compared
to that.  One thing that I'd love is a way to express that yes, there
are maintainers, and no you should not Cc them but just send the
patches to the list.  Maybe even with a core files vs drivers split
as suggested by you above.  But compared to the messed up git
heuristics that is pretty much a minor issue.

[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux