From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Matt Mackall <mpm@selenic.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Subject: Re: make checkstack on m68k
Date: Fri, 18 Jun 2004 18:06:04 +0200 [thread overview]
Message-ID: <20040618160604.GA29579@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0406190137400.31712@bonkers.disegno.com.au>
On Sat, 19 June 2004 01:59:27 +1000, Finn Thain wrote:
>
> Jörn, the best thing about my hack was that it didn't interfere with the
> regexes for the other archs. Andreas better solved that problem by
> providing the result in $1, by using some foreknowlegde of the objdump
> output format.
>
> I whole-heartedly endorse the signed-off-by-Geert and provided-by-Andreas
> patch on the basis of even less interference with the existing code. i.e.
>
> http://lkml.org/lkml/2004/6/18/104
Hmm, convinced. My perl skills were simply not good enough to see
through all the tricks. Patch is accepted, I'll integrate and forward
after the weekend.
Jörn
--
"Error protection by error detection and correction."
-- from a university class
prev parent reply other threads:[~2004-06-18 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200406161930.VAA16618@pfultra.phil.uni-sb.de>
2004-06-17 8:43 ` Finn Thain
2004-06-17 18:36 ` Jörn Engel
2004-06-17 19:27 ` Geert Uytterhoeven
2004-06-18 12:18 ` Jörn Engel
2004-06-18 13:39 ` Geert Uytterhoeven
2004-06-18 13:43 ` Jörn Engel
2004-06-18 15:59 ` Finn Thain
2004-06-18 16:06 ` Jörn Engel [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=20040618160604.GA29579@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mpm@selenic.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
all inboxes | Powered by JetHome®