From: Hui Zhu <teawater@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Hui Zhu <hui.zhu@windriver.com>, Michal Marek <mmarek@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
ozan@pardus.org.tr, Matthew Wilcox <willy@linux.intel.com>,
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 12:03:00 +0800 [thread overview]
Message-ID: <daef60381001282003q4d43c01dk91c53ec5be17fdf2@mail.gmail.com> (raw)
In-Reply-To: <20100128181240.GA9174@merkur.ravnborg.org>
On Fri, Jan 29, 2010 at 02:12, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Thu, Jan 28, 2010 at 02:58:02PM +0800, Hui Zhu wrote:
>> Sorry guys, the prev mail for this patch is ugly.
>> I make a new mail for it.
>
> Random updates to scripts/* historically often go
> in via the kbuild tree, so Michal added.
>
> Sam
>
> [Kept rest of mail so Michal can see it]
>
>>
Thanks Sam. And I make a small patch to make get_script.pl can output
Michal Marek.
Hui
Signed-off-by: Hui Zhu <teawater@gmail.com>
---
MAINTAINERS | 4 ++++
1 file changed, 4 insertions(+)
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3086,6 +3086,10 @@ L: autofs@linux.kernel.org
S: Maintained
F: fs/autofs4/
+KERNEL SCRIPT
+M: Michal Marek <mmarek@suse.cz>
+F: scripts/*
+
KERNEL BUILD
M: Michal Marek <mmarek@suse.cz>
T: git git://repo.or.cz/linux-kbuild.git for-next
next prev parent reply other threads:[~2010-01-29 4:03 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 [this message]
[not found] ` <1264739206.10856.8.camel@Joe-Laptop.home>
2010-01-29 5:45 ` Hui Zhu
2010-01-29 13:31 ` Michal Marek
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=daef60381001282003q4d43c01dk91c53ec5be17fdf2@mail.gmail.com \
--to=teawater@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=hui.zhu@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=ozan@pardus.org.tr \
--cc=sam@ravnborg.org \
--cc=willy@linux.intel.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.