From: Andrew Morton <akpm@linux-foundation.org>
To: Hui Zhu <teawater@gmail.com>
Cc: "Arjan van de Ven" <arjan@linux.intel.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Ozan Çaglayan" <ozan@pardus.org.tr>,
"Matthew Wilcox" <willy@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add options to markup_oops.pl to make it support cross-compiler environment better
Date: Fri, 22 Jan 2010 17:26:15 -0800 [thread overview]
Message-ID: <20100122172615.4a560908.akpm@linux-foundation.org> (raw)
In-Reply-To: <daef60381001170538o5b3b0b17l72923261b76d521@mail.gmail.com>
On Sun, 17 Jan 2010 21:38:28 +0800
Hui Zhu <teawater@gmail.com> wrote:
> Hello,
>
> The markup_oops.pl have 2 troubles to support cross-compiler environment:
> 1. It use objdump directly.
> 2. It use modinfo to get the message of module.
>
> This patch add 2 options to markup_oops.pl:
> 1. -c CROSS_COMPILE Specify the prefix used for toolchain.
> 2. -m MODULE_DIRNAME Specify the module directory name.
>
> After this patch, parse the x8664 oops in x86, we can:
> cat amd64m | perl ~/kernel/tmp/m.pl -c
> /home/teawater/kernel/bin/x8664- -m ./e.ko vmlinux
>
The other patches are wordwrapped and one still didn't apply after
fixing that, so please just redo and resend everything. Send them to
yourself first and check that the result still applies OK.
Also, we prefer patch titles to be of the form
subsystem-identifier: what was changed
so a good title for this patch would have been
markup_oops.pl: add options to improve cross-sompilation environments
Thanks.
next prev parent reply other threads:[~2010-01-23 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 13:38 [PATCH] Add options to markup_oops.pl to make it support cross-compiler environment better Hui Zhu
2010-01-23 1:26 ` Andrew Morton [this message]
2010-01-25 7:39 ` Hui Zhu
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=20100122172615.4a560908.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
--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