[PATCH] [465/2many] MAINTAINERS - SUPERH64 (sh64)

[PATCH] [465/2many] MAINTAINERS - SUPERH64 (sh64)

[joe]

Add file pattern to MAINTAINER entry

Signed-off-by: Joe Perches <joe@perches.com>

diff --git a/MAINTAINERS b/MAINTAINERS
index f42712c..df097fb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4423,6 +4423,8 @@ M:	lethal@linux-sh.org
 L:	linuxsh-shmedia-dev@lists.sourceforge.net
 W:	http://www.linux-sh.org
 S:	Maintained
+F:	arch/sh64/
+F:	arch/asm-sh64/
 
 SUN3/3X
 P:	Sam Creasey

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

[joe]

Add file pattern to MAINTAINER entry

Signed-off-by: Joe Perches <joe@perches.com>

diff --git a/MAINTAINERS b/MAINTAINERS
index 3e51fc6..f42712c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4414,6 +4414,8 @@ 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:	arch/asm-sh/
 
 SUPERH64 (sh64)
 P:	Paul Mundt

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

[Paul Mundt]

On Sun, Aug 12, 2007 at 11:36:51PM -0700, joe@perches.com wrote:
> Add file pattern to MAINTAINER entry
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3e51fc6..f42712c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4414,6 +4414,8 @@ 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:	arch/asm-sh/
>  
I suppose you meant include/ here?

On Sun, Aug 12, 2007 at 11:36:53PM -0700, joe@perches.com wrote:
> Add file pattern to MAINTAINER entry
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f42712c..df097fb 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4423,6 +4423,8 @@ M:	lethal@linux-sh.org
>  L:	linuxsh-shmedia-dev@lists.sourceforge.net
>  W:	http://www.linux-sh.org
>  S:	Maintained
> +F:	arch/sh64/
> +F:	arch/asm-sh64/
>  

Likewise?

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?

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.

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

[Joe Perches]

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