From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <ft01@webmastery.com.au>,
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 15:43:13 +0200 [thread overview]
Message-ID: <20040618134313.GG18258@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0406181537210.11779@waterleaf.sonytel.be>
On Fri, 18 June 2004 15:39:38 +0200, Geert Uytterhoeven wrote:
> On Fri, 18 Jun 2004, [iso-8859-1] Jörn Engel wrote:
> > On Thu, 17 June 2004 21:27:35 +0200, Geert Uytterhoeven wrote:
> > > On Thu, 17 Jun 2004, [iso-8859-1] Jörn Engel wrote:
> > > >
> > > > It's not as ugly as my hack. Can I get a success report from m68k?
> > > > Thanks!
> >
> > Good. Finn, can you resend to me with a signed-off-by: comment? If
> > you grow bored, you could seperate the i386 regexes (sub..., add...)
> > as well.
>
> If you insist...
>
> Add m68k support to checkstack.pl
>
> Regular expression combination by Andres Schwab
Ah, no. I really wanted Finn's version with two seperate regexes,
it's much cleaner. An array of regexes might be the best, but in a
perfect world, we would have compiler support instead, so I don't mind
a little ugliness.
Jörn
--
Courage is not the absence of fear, but rather the judgement that
something else is more important than fear.
-- Ambrose Redmoon
next prev parent reply other threads:[~2004-06-18 13:43 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 [this message]
2004-06-18 15:59 ` Finn Thain
2004-06-18 16:06 ` Jörn Engel
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=20040618134313.GG18258@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=ft01@webmastery.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®