From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Hui Zhu <teawater@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Sam Ravnborg <sam@ravnborg.org>,
Matthew Wilcox <willy@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix markup_oops.pl get error in x86
Date: Wed, 06 Jan 2010 15:45:25 +0200 [thread overview]
Message-ID: <4B4493F5.9010308@pardus.org.tr> (raw)
In-Reply-To: <daef60381001060123vbb09aecy7943d72fcb8278a@mail.gmail.com>
Hui Zhu wrote On 06-01-2010 11:23:
> Hello,
>
> When I try to use markup_oops.pl in x86, I always get:
I already mentioned that but wasn't able to get attention, and yes the current code doesn't work,
http://lkml.indiana.edu/hypermail/linux/kernel/0908.0/02222.html
prev parent reply other threads:[~2010-01-06 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 9:23 [PATCH] Fix markup_oops.pl get error in x86 Hui Zhu
2010-01-06 13:23 ` Arjan van de Ven
2010-01-07 5:43 ` Hui Zhu
2010-01-07 13:03 ` Arjan van de Ven
2010-01-11 2:59 ` Hui Zhu
2010-01-12 3:02 ` Hui Zhu
2010-01-06 13:45 ` Ozan Çağlayan [this message]
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=4B4493F5.9010308@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=teawater@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox