From: Juan Quintela <quintela@mandrakesoft.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Vivien Chappelier <vivienc@nerim.net>,
Ralf Baechle <ralf@linux-mips.org>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: sigset_t32 broken?
Date: Mon, 27 Jan 2003 23:30:15 +0100 [thread overview]
Message-ID: <86smvez0nc.fsf@trasno.mitica> (raw)
In-Reply-To: <Pine.GSO.4.21.0301271019030.6130-100000@vervain.sonytel.be> (Geert Uytterhoeven's message of "Mon, 27 Jan 2003 10:19:26 +0100 (MET)")
>>>>> "geert" == Geert Uytterhoeven <geert@linux-m68k.org> writes:
geert> On Mon, 27 Jan 2003, Vivien Chappelier wrote:
>> On Fri, 24 Jan 2003, Ralf Baechle wrote:
>> > Most of what your patch does is undoing an accidental commit of a signal
>> > rework that wasn't yet supposed to go out.
>>
>> Maybe.. but current version is still wrong :) The type of the sig
>> array in the 32-bit compatibility struct sigset_t32 must be 32bit long,
>> i.e. unsigned int not unsigned long.
>> And I think unsigned describes the data better than signed, but that's a
>> matter of taste :) (coherent with the choice in asm-mips/signal.h).
geert> Why not make it u32?
Nahh, that will make it clear indeed to stupid's like me :p
Later ,Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
prev parent reply other threads:[~2003-01-27 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 7:17 sigset_t32 broken? Andrew Clausen
2003-01-23 9:59 ` Vivien Chappelier
2003-01-24 1:48 ` Ralf Baechle
2003-01-27 0:44 ` Vivien Chappelier
2003-01-27 9:19 ` Geert Uytterhoeven
2003-01-27 22:30 ` Juan Quintela [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=86smvez0nc.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=vivienc@nerim.net \
/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.