Re: [PATCH] markup_oops.pl: fix get "No matching code found" when first line of range is the faulting instruction

[Michal Marek]

Hui Zhu napsal(a):
> What about this?
> 
> Signed-off-by: Hui Zhu <teawater@xxxxxxxxx>
> 
> ---
>  MAINTAINERS |    2 ++
>  1 file changed, 2 insertions(+)
> 
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3095,6 +3095,8 @@ S:	Maintained
>  F:	Documentation/kbuild/
>  F:	Makefile
>  F:	scripts/Makefile.*
> +F:	scripts/markup_oops.pl
> +F:	scripts/mk*
> 
>  KERNEL JANITORS
>  L:	kernel-janitors@xxxxxxxxxxxxxxx

(somehow I was un-CCed again)

I don't know if we really need to mention every single script that has
no "real" maintainer in the kbuild section. As noted by Joe, adding
scripts/* is also not a good idea. scripts/get_maintainer.pl parses
Signed-off-by: lines, so after the first commit, my email should appear
in the output anyway. For people reading the MAINTAINERS file
themselves, what about this one?

Subject: [PATCH] MAINTAINERS: add a few more patterns to kbuild

Also, add a note that "unmaintained" files below scripts/ should go via
the kbuild tree (best current practice).

Signed-off-by: Michal Marek <mmarek@xxxxxxx>

diff --git a/MAINTAINERS b/MAINTAINERS
index c8f47bf..f0c3e2f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3088,7 +3088,7 @@ L:        autofs@xxxxxxxxxxxxxxxx
 S:     Maintained
 F:     fs/autofs4/

-KERNEL BUILD
+KERNEL BUILD + files below scripts/ (unless maintained elsewhere)
 M:     Michal Marek <mmarek@xxxxxxx>
 T:     git git://repo.or.cz/linux-kbuild.git for-next
 T:     git git://repo.or.cz/linux-kbuild.git for-linus
@@ -3097,6 +3097,9 @@ S:        Maintained
 F:     Documentation/kbuild/
 F:     Makefile
 F:     scripts/Makefile.*
+F:     scripts/basic/
+F:     scripts/mk*
+F:     scripts/package/

 KERNEL JANITORS
 L:     kernel-janitors@xxxxxxxxxxxxxxx

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