* special include/asm/siginfo.h for MIPS
@ 2003-05-21 2:11 Jun Sun
2003-05-27 12:48 ` Ralf Baechle
0 siblings, 1 reply; 2+ messages in thread
From: Jun Sun @ 2003-05-21 2:11 UTC (permalink / raw)
To: linux-mips; +Cc: jsun
MIPS has different values from all other arches in this file.
(such as SIGEV_NONE, etc) Does anybody know why?
Because of this in 2.5 everybody else now goes to use the
the generic version of siginfo, while MIPS uses its own special
version.
Even worse the new usage of SIGEV_XXX seems to suggest
sigev_notify is bitwise-or'ed flag instead of enumeration of integers.
This is in a direct conflict with current MIPS values.
Any thoughts? Can we just use what other arches are using?
Jun
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: special include/asm/siginfo.h for MIPS
2003-05-21 2:11 special include/asm/siginfo.h for MIPS Jun Sun
@ 2003-05-27 12:48 ` Ralf Baechle
0 siblings, 0 replies; 2+ messages in thread
From: Ralf Baechle @ 2003-05-27 12:48 UTC (permalink / raw)
To: Jun Sun; +Cc: linux-mips
On Tue, May 20, 2003 at 07:11:24PM -0700, Jun Sun wrote:
> Any thoughts? Can we just use what other arches are using?
No. Changing the Linux ABI is not an option without forcing reason
unless you somehow can show that some interface simply wasn't used.
Ralf
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-05-27 12:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-21 2:11 special include/asm/siginfo.h for MIPS Jun Sun
2003-05-27 12:48 ` Ralf Baechle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox