All of lore.kernel.org
 help / color / mirror / Atom feed
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] Fix markup_oops.pl get $func_offset error in x8664
Date: Fri, 22 Jan 2010 17:21:08 -0800	[thread overview]
Message-ID: <20100122172108.620deddc.akpm@linux-foundation.org> (raw)
In-Reply-To: <daef60381001170535q6abfd29cp1b8d07709c00e1db@mail.gmail.com>

On Sun, 17 Jan 2010 21:35:25 +0800
Hui Zhu <teawater@gmail.com> wrote:

> This patch like the prev patch in http://lkml.org/lkml/2010/1/6/57
> The x8664 part have the same trouble with it.  This patch is to fix it.
> 

This changelog isn't very useful.  Please provide a description for this
change which doesn't require that people have to go off and read the
internet and then work out how some other patch is relevant to this
one!


> ---
>  scripts/markup_oops.pl |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- a/scripts/markup_oops.pl
> +++ b/scripts/markup_oops.pl
> @@ -158,7 +158,7 @@ while (<STDIN>) {
>  		$function = $1;
>  		$func_offset = $2;
>  	}
> -	if ($line =~ /RIP: 0010:\[\<[0-9a-f]+\>\]  \[\<[0-9a-f]+\>\]
> ([a-zA-Z0-9\_]+)\+(0x[0-9a-f]+)\/0x[a-f0-9]/) {
> +	if ($line =~ /RIP: 0010:\[\<[0-9a-f]+\>\]  \[\<[0-9a-f]+\>\]
> ([a-zA-Z0-9\_]+)\+0x([0-9a-f]+)\/0x[a-f0-9]/) {
>  		$function = $1;
>  		$func_offset = $2;
>  	}

Your email client wordwrapped the patch.  Please fix it then resend.


  reply	other threads:[~2010-01-23  1:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 13:35 [PATCH] Fix markup_oops.pl get $func_offset error in x8664 Hui Zhu
2010-01-23  1:21 ` Andrew Morton [this message]
2010-01-25  6:14   ` Hui Zhu
  -- strict thread matches above, loose matches on Subject: below --
2010-01-25 14:27 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=20100122172108.620deddc.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 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.