From: Jun Sun <jsun@mvista.com>
To: linux-mips@linux-mips.org
Cc: jsun@mvista.com
Subject: special include/asm/siginfo.h for MIPS
Date: Tue, 20 May 2003 19:11:24 -0700 [thread overview]
Message-ID: <20030520191124.N32567@mvista.com> (raw)
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
next reply other threads:[~2003-05-21 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 2:11 Jun Sun [this message]
2003-05-27 12:48 ` special include/asm/siginfo.h for MIPS Ralf Baechle
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=20030520191124.N32567@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
/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