On Fri, Jun 23, 2017 at 12:39:36PM -0600, Jonathan Corbet wrote:

> I can continue in this mode, but I do wonder if there's a better way out
> there somewhere.  So I think there would be value in a session on the
> maintenance of "subsystems" that don't fit neatly into the kernel
> source-tree hierarchy.

One thing I think it'd be good to do is work out a sensible way of
keeping the maintainers of the relevant subsystems in the loop on things
- a combination of the mechanics and how much effort we want to put into
making sure people have at least seen things.  For example it looks like
the regulator DocBook got converted to RST without me being aware of it
(it seems I did get copied on one mail at some point but I can't have
read it and there don't seem to have been any resends), that case isn't
a problem itself but it seems like an area where things could end up not
running smoothly.

I know I rely fairly heavily on subject lines to filter what I'm looking
at since some of my subsystems mean that I get copied on lots of random
stuff that's of at most passing relevance to me which ends up being an
issue with things like DT bindings sometimes (I think this is also part
of what went wrong with the regulator conversion) but that doesn't
scale since the subject lines can't easily be useful for multiple
subsystems simultaneously.  I'm not sure what else to do though, we
basically only have the subject lines and CC lists to work with here.