Re: [PATCH] [464/2many] MAINTAINERS - SUPERH (sh)

[Joe Perches <joe@perches.com>]

On Tue, 2007-08-14 at 09:43 +0900, Paul Mundt wrote:
> On Sun, Aug 12, 2007 at 11:36:51PM -0700, joe@perches.com wrote:
> I suppose you meant include/ here?

Yes.  Thanks.  I've replace them with this in my tree.

SUPERH (sh)
P:	Paul Mundt
M:	lethal@linux-sh.org
L:	linuxsh-dev@lists.sourceforge.net (subscribers-only)
W:	http://www.linux-sh.org
S:	Maintained
F:	arch/sh/
F:	include/asm-sh/

SUPERH64 (sh64)
P:	Paul Mundt
M:	lethal@linux-sh.org
L:	linuxsh-shmedia-dev@lists.sourceforge.net
W:	http://www.linux-sh.org
S:	Maintained
F:	arch/sh64/
F:	include/asm-sh64/

> The more pressing question that comes to mind is what the point of this
> is? Architecture related drivers and things of that nature fall under
> this also, as most folks don't create a separate entry for every trivial
> driver. Are you intending to have a long list of individual drivers here
> that your script can parse?

If there are separate maintainers, sure.
Look at drivers/foo for instance.

> Is there actually a problem with people just opening up MAINTAINERS in a
> text file? Surely this is not such a non-intuitive thing, there are
> already keywords there you can grep for.

It's an automation problem.  It's just for CC's.

cheers,  Joe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/