Re: Linux-hotplug needs an official maintainer. Am I right?

[David Brownell <david-b@pacbell.net>]

> > Since the hotplug implementation effort will include some
> > ongoing general architecture work in addition to bus-specific
> > work, perhaps we need a maintainer for the generic pieces, 
> > while the bus-specific patches get routed through the bus
> > maintainers.  Does this make sense?

I'm not sure we know yet whether Linus is looking for that.  And
there really aren't many "generic" pieces; call_usermodehelper()
is about all, but linux-hotplug can't own "kmod.c" (I'd suspect).

The issue I see is the need to make sure the coordination gets
done -- like updating modutils before integrating an ABI change.
And that seems like a pretty broad Linux development issue.


> If David doesn't want to do it, I'll volunteer.  He has done the most
> work on it so far and deserves it.

Or maybe a break from it?  :-)  Thanks!  I'd like to hear from
Linus on this topic before I say more.

- Dave


> However, remember that the maintainer tends to have development time
> decrease, just ask Randy about being the USB maintainer :)
>
> Also this looks like more of a coordination job, as all of the
> individual pieces are all covered by other people, and the main job will
> be notifying the current maintainers, and getting their buy in.




_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel