From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: grundler@parisc-linux.org, jsoe0708@tiscali.be,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] warning: minor abi change
Date: Mon, 7 Jul 2003 21:45:51 -0400 [thread overview]
Message-ID: <20030708014551.GB21801@systemhalted> (raw)
In-Reply-To: <200307072019.h67KJDMa002052@hiauly1.hia.nrc.ca>
> > I can't really come up with a scenario where userspace passes a function
> > pointer to the kernel and has the kernel call or compare the function
> > pointer?
>
> One example is sigaction.
Fixable, I can stick a sigaction wrapper in userspace. Should we though?
c.
next prev parent reply other threads:[~2003-07-08 1:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030627151546.GA30607@dsl2.external.hp.com>
[not found] ` <3ED70CF10000AE2E@ocpmta2.freegates.net>
2003-06-27 16:54 ` [parisc-linux] warning: minor abi change Grant Grundler
2003-06-28 10:48 ` Joel Soete
2003-07-05 23:08 ` Grant Grundler
2003-07-05 23:53 ` John David Anglin
2003-07-06 4:12 ` Grant Grundler
2003-07-06 16:12 ` Joel Soete
2003-07-07 20:02 ` Carlos O'Donell
2003-07-07 20:19 ` John David Anglin
2003-07-08 1:45 ` Carlos O'Donell [this message]
2003-07-06 5:57 ` [parisc-linux] IDE modules build prob Grant Grundler
2003-07-06 6:31 ` Grant Grundler
2003-07-06 7:23 ` Alan Cox
[not found] <20030711065156.GA17025@dsl2.external.hp.com>
2003-07-11 8:26 ` [parisc-linux] warning: minor abi change Joel Soete
2003-07-11 10:24 ` Alan Cox
2003-06-26 13:54 Matthew Wilcox
2003-06-26 17:03 ` Joel Soete
2003-06-26 17:06 ` Matthew Wilcox
2003-06-26 17:45 ` Randolph Chung
2003-06-27 14:41 ` Joel Soete
2003-06-27 16:21 ` Joel Soete
2003-06-27 16:52 ` Alan Cox
2003-07-07 16:00 ` Joel Soete
2003-07-07 16:05 ` Alan Cox
2003-07-07 16:31 ` Matthew Wilcox
2003-07-07 16:39 ` Joel Soete
2003-07-07 16:33 ` Joel Soete
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=20030708014551.GB21801@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@parisc-linux.org \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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