From: Michal Marek <mmarek@suse.cz>
To: Hui Zhu <teawater@gmail.com>
Cc: Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] markup_oops.pl: fix get "No matching code found" when first line of range is the faulting instruction
Date: Fri, 29 Jan 2010 14:31:33 +0100 [thread overview]
Message-ID: <4B62E335.8010207@suse.cz> (raw)
In-Reply-To: <daef60381001282145q39f6fcd8s340e1d74f2466426@mail.gmail.com>
Hui Zhu napsal(a):
> What about this?
>
> Signed-off-by: Hui Zhu <teawater@gmail.com>
>
> ---
> 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@vger.kernel.org
(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@suse.cz>
diff --git a/MAINTAINERS b/MAINTAINERS
index c8f47bf..f0c3e2f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3088,7 +3088,7 @@ L: autofs@linux.kernel.org
S: Maintained
F: fs/autofs4/
-KERNEL BUILD
+KERNEL BUILD + files below scripts/ (unless maintained elsewhere)
M: Michal Marek <mmarek@suse.cz>
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@vger.kernel.org
next prev parent reply other threads:[~2010-01-29 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 6:58 [PATCH] markup_oops.pl: fix get "No matching code found" when first line of range is the faulting instruction Hui Zhu
2010-01-28 18:12 ` Sam Ravnborg
2010-01-29 4:03 ` Hui Zhu
[not found] ` <1264739206.10856.8.camel@Joe-Laptop.home>
2010-01-29 5:45 ` Hui Zhu
2010-01-29 13:31 ` Michal Marek [this message]
2010-01-29 13:13 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B62E335.8010207@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=teawater@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.