* [PATCH] [497/2many] MAINTAINERS - USB HUB DRIVER
@ 2007-08-13 6:38 joe
2007-08-13 7:24 ` [linux-usb-devel] " David Brownell
0 siblings, 1 reply; 3+ messages in thread
From: joe @ 2007-08-13 6:38 UTC (permalink / raw)
To: torvalds, linux-usb-users, linux-usb-devel, linux-kernel, johannes, akpm
Add file pattern to MAINTAINER entry
Signed-off-by: Joe Perches <joe@perches.com>
diff --git a/MAINTAINERS b/MAINTAINERS
index 270952c..d46c083 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4705,6 +4705,7 @@ M: johannes@erdfelt.com
L: linux-usb-users@lists.sourceforge.net
L: linux-usb-devel@lists.sourceforge.net
S: Maintained
+F: drivers/usb/core/hub.*
USB ISP116X DRIVER
P: Olav Kongas
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-usb-devel] [PATCH] [497/2many] MAINTAINERS - USB HUB DRIVER
2007-08-13 6:38 [PATCH] [497/2many] MAINTAINERS - USB HUB DRIVER joe
@ 2007-08-13 7:24 ` David Brownell
2007-08-13 14:16 ` Stefan Richter
0 siblings, 1 reply; 3+ messages in thread
From: David Brownell @ 2007-08-13 7:24 UTC (permalink / raw)
To: joe
Cc: linux-usb-devel, torvalds, linux-usb-users, linux-kernel, johannes, akpm
On Sunday 12 August 2007, joe@perches.com wrote:
> Add file pattern to MAINTAINER entry
>
> Signed-off-by: Joe Perches <joe@perches.com>
>
I seem to be missing some context for these "2many" patches; and
don't really see any in the MARC archives either. This seems like
about 600 patches out of the blue. A lot for RC3, even if it is
"just" for the MAINTAINERS file.
Is the motivation here purely to make it easier to find out how to
report bugs and suggest improvements? If so, that seems like only
one of many related issues ...
Is there general agreement that these "F:" entries should be used?
Rather than, say, embedding references in the relevant parts of
the source tree, adjacent to those files, where they would be more
visible to people making relevant changes.
I'm also concerned with the reality that the MAINTAINERS file is
not accurate. The $SUBJECT patch is one example; the named maintainer
is no longer active (in that area, at least) and the named driver is
not actually separable from the rest of usbcore. Better IMO to just
remove the "hub driver" entry.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-usb-devel] [PATCH] [497/2many] MAINTAINERS - USB HUB DRIVER
2007-08-13 7:24 ` [linux-usb-devel] " David Brownell
@ 2007-08-13 14:16 ` Stefan Richter
0 siblings, 0 replies; 3+ messages in thread
From: Stefan Richter @ 2007-08-13 14:16 UTC (permalink / raw)
To: David Brownell
Cc: joe, linux-usb-devel, torvalds, linux-usb-users, linux-kernel,
johannes, akpm
David Brownell wrote:
> Is there general agreement that these "F:" entries should be used?
> Rather than, say, embedding references in the relevant parts of
> the source tree, adjacent to those files, where they would be more
> visible to people making relevant changes.
>
> I'm also concerned with the reality that the MAINTAINERS file is
> not accurate. The $SUBJECT patch is one example; the named maintainer
> is no longer active (in that area, at least) and the named driver is
> not actually separable from the rest of usbcore. Better IMO to just
> remove the "hub driver" entry.
I don't speak for Joe, but: If there is a good mapping from MAINTAINERS
to paths then more submitters will use MAINTAINERS more frequently. A
side effect would be that outdated entries in MAINTAINERS would become
apparent more quickly, and updated more quickly. Of course that's just
speculation --- but your comment on this "hub driver" entry, prompted by
Joe's patch, seems to support that speculation.
--
Stefan Richter
-=====-=-=== =--- -==-=
http://arcgraph.de/sr/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-08-13 15:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-08-13 6:38 [PATCH] [497/2many] MAINTAINERS - USB HUB DRIVER joe
2007-08-13 7:24 ` [linux-usb-devel] " David Brownell
2007-08-13 14:16 ` Stefan Richter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®