From: Daniel Jacobowitz <dan@debian.org>
To: Bradley Bozarth <bbozarth@cisco.com>
Cc: linux-mips@linux-mips.org, george@mvista.com
Subject: Re: SEGEV defines
Date: Thu, 7 Nov 2002 17:10:29 -0500 [thread overview]
Message-ID: <20021107221029.GA22385@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0211071229340.7794-100000@bbozarth-lnx.cisco.com>
Presumably they match IRIX... like the rest of MIPS's oddball
definitions. A little hard to change them now.
On Thu, Nov 07, 2002 at 12:33:55PM -0800, Bradley Bozarth wrote:
> Can these be changed?
>
> > Now a question, why does mips use these values:
> > #define SIGEV_SIGNAL 129 /* notify via signal */
> > #define SIGEV_CALLBACK 130 /* ??? */
> > #define SIGEV_THREAD 131 /* deliver via thread
> > creation */
> >
> > It is the only platform that adds anything to the simple
> > 1,2,3 values used on other platforms. The reason I ask, is
> > that I would like to change them to conform to all the
> > others.
>
>
>
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-07 22:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 18:35 make xmenuconfig is broken Jun Sun
2002-10-29 19:24 ` Karsten Merker
2002-10-29 21:30 ` Jun Sun
2002-10-30 13:07 ` Maciej W. Rozycki
2002-11-07 19:26 ` Maciej W. Rozycki
2002-11-07 20:33 ` SEGEV defines Bradley Bozarth
2002-11-07 22:10 ` Daniel Jacobowitz [this message]
2002-11-07 22:23 ` make xmenuconfig is broken Jun Sun
2002-11-08 12:25 ` Maciej W. Rozycki
2002-11-08 17:35 ` Ralf Baechle
2002-11-08 18:30 ` Maciej W. Rozycki
2002-11-08 19:31 ` Ralf Baechle
2002-10-30 15:58 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 9:14 SEGEV defines Tor Arntsen
2002-11-14 2:11 ` Bradley Bozarth
2002-11-14 4:23 ` george anzinger
2002-11-14 4:51 ` Ralf Baechle
2002-11-15 0:43 ` Bradley Bozarth
2002-11-15 0:43 ` Bradley Bozarth
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=20021107221029.GA22385@nevyn.them.org \
--to=dan@debian.org \
--cc=bbozarth@cisco.com \
--cc=george@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 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.