From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: linux-mips@linux-mips.org, Franck Bui-Huu <fbuihuu@gmail.com>
Subject: Re: [PATCH 3/7] signal: clean up sigframe structure
Date: Tue, 23 Jan 2007 17:17:03 +0000 [thread overview]
Message-ID: <20070123171703.GA26510@linux-mips.org> (raw)
In-Reply-To: <cda58cb80701230700j70f8e447o27f64091be9d57f5@mail.gmail.com>
On Tue, Jan 23, 2007 at 04:00:42PM +0100, Franck Bui-Huu wrote:
> and didn't notice that the symbol could be defined to 0 below. I'll
> fix it but just for my information what the point to do this ?
Some of the _WAR constants are used in if statements which produces much
less messy looking code than piles of #ifdefs.
Ralf
next prev parent reply other threads:[~2007-01-23 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 14:18 [PATCH 0/7] Clean up signal code Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 1/7] signals: reduce {setup,restore}_sigcontext sizes Franck Bui-Huu
2007-01-23 14:38 ` Ralf Baechle
2007-01-23 16:26 ` Franck Bui-Huu
2007-01-23 16:36 ` Ralf Baechle
2007-01-24 12:25 ` Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 2/7] signal: do not inline functions in signal-common.h Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 3/7] signal: clean up sigframe structure Franck Bui-Huu
2007-01-23 14:35 ` Ralf Baechle
2007-01-23 15:00 ` Franck Bui-Huu
2007-01-23 17:17 ` Ralf Baechle [this message]
2007-01-23 14:18 ` [PATCH 4/7] signal32: remove code duplication Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 5/7] signal: test return value of install_sigtramp() Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 6/7] signal: factorize debug code Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 7/7] signal32: reduce {setup,restore}_sigcontext32 sizes Franck Bui-Huu
2007-01-23 14:32 ` [PATCH 0/7] Clean up signal code Ralf Baechle
2007-01-23 14:54 ` Franck Bui-Huu
2007-01-23 14:58 ` Daniel Jacobowitz
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=20070123171703.GA26510@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=fbuihuu@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=vagabon.xyz@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.