All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: matthieu.castet@parrot.com, linux-kernel@vger.kernel.org,
	arnd@arndb.de, tarmigan@gmail.com
Subject: Re: [PATCH][Checkstack] Don't censor output
Date: Thu, 9 Apr 2009 16:39:48 -0700	[thread overview]
Message-ID: <20090409163948.b39e40cd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090406211146.GA10231@logfs.org>

On Mon, 6 Apr 2009 23:11:46 +0200
J__rn Engel <joern@logfs.org> wrote:

> Subject: [PATCH][Checkstack] Don't censor output

Please use the form

	subsytem-identifier: what-i-did-to-it

so

	[patch] checkstack: don't censor output

would suit here.

> Date: Mon, 6 Apr 2009 23:11:46 +0200
> User-Agent: Mutt/1.5.13 (2006-08-11)
> 
> For reasons that neither Arnd nor I can remember, the s390 port of
> checkstack happened to ignore stack frames below 300 and above 10000
> bytes.  Later on the same effect - arguably a bug - was copied into the
> arm, ia64, mips and sh64 ports.
> 
> Fixing it also makes the regular expressions shorter and simpler.
> 
>  scripts/checkstack.pl |   12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> --- debuggerhead/scripts/checkstack.pl~checkstack	2008-03-05 12:14:05.000000000 +0100
> +++ debuggerhead/scripts/checkstack.pl	2008-11-04 20:38:08.000000000 +0100

The patch fails to apply, yet nobody has changed checkstack.pl in ages.
I think you're tricking me.


      reply	other threads:[~2009-04-09 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 21:11 [PATCH][Checkstack] Don't censor output Jörn Engel
2009-04-09 23:39 ` Andrew Morton [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=20090409163948.b39e40cd.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthieu.castet@parrot.com \
    --cc=tarmigan@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.