From: Pete Zaitcev <zaitcev@redhat.com>
To: bidulock@openss7.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: export of sys_call_table
Date: Tue, 8 Oct 2002 20:30:29 -0400 [thread overview]
Message-ID: <200210090030.g990UTe08202@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1034119380.19047.linux-kernel2news@redhat.com>
> Following is a tested patch for i386 architecture for registration
> of putpmsg and getpmsg system calls. This version (courtesy of
> Dave Grothe at GCOM) uses up/down semaphore instead of read/write
> spinlocks. The patch is against 2.4.19 but should apply up and
> down a ways as well.
> +EXPORT_SYMBOL(register_streams_calls);
> +EXPORT_SYMBOL(unregister_streams_calls);
EXPORT_SYMBOL_GPL perhaps? Otherwise it's just a disguised hook,
just like nVidia's shell driver.
> +static rwlock_t streams_call_lock = RW_LOCK_UNLOCKED;
Does not look like a semaphore to me...
-- Pete
next prev parent reply other threads:[~2002-10-09 0:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021003153943.E22418@openss7.org.suse.lists.linux.kernel>
[not found] ` <1033682560.28850.32.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
[not found] ` <20021003170608.A30759@openss7.org.suse.lists.linux.kernel>
[not found] ` <1033722612.1853.1.camel@localhost.localdomain.suse.lists.linux.kernel>
[not found] ` <20021004051932.A13743@openss7.org.suse.lists.linux.kernel>
2002-10-04 13:01 ` export of sys_call_table Andi Kleen
2002-10-04 13:11 ` Brian F. G. Bidulock
2002-10-04 13:15 ` Andi Kleen
2002-10-04 13:22 ` Brian F. G. Bidulock
2002-10-04 14:11 ` Andi Kleen
2002-10-04 14:31 ` Brian F. G. Bidulock
[not found] ` <20021003221525.GA2221@kroah.com.suse.lists.linux.kernel>
[not found] ` <20021003222716.GB14919@suse.de.suse.lists.linux.kernel>
[not found] ` <1033684027.1247.43.camel@phantasy.suse.lists.linux.kernel>
[not found] ` <20021003233504.GA20570@suse.de.suse.lists.linux.kernel>
[not found] ` <20021003235022.GA82187@compsoc.man.ac.uk.suse.lists.linux.kernel>
[not found] ` <mailman.1033691043.6446.linux-kernel2news@redhat.com.suse.lists.linux.kernel>
[not found] ` <200210040403.g9443Vu03329@devserv.devel.redhat.com.suse.lists.linux.kernel>
[not found] ` <20021003233221.C31444@openss7.org.suse.lists.linux.kernel>
[not found] ` <20021004133657.B17216@devserv.devel.redhat.com.suse.lists.linux.kernel>
2002-10-04 18:14 ` Andi Kleen
2002-10-04 18:46 ` Alan Cox
2002-10-04 18:45 ` Alexander Viro
2002-10-04 19:15 ` Brian F. G. Bidulock
2002-10-04 19:26 ` Andi Kleen
2002-10-04 19:37 ` Pete Zaitcev
2002-10-04 20:17 ` (off-list) Mail headers (was: Re: export of sys_call_table) Sean Neakums
2002-10-04 20:33 ` Sean Neakums
2002-10-04 19:43 ` export of sys_call_table Robert Love
2002-10-04 22:21 ` David S. Miller
2002-10-04 22:41 ` Brian F. G. Bidulock
2002-10-04 22:38 ` David S. Miller
2002-10-08 22:20 ` [PATCH] " Brian F. G. Bidulock
2002-10-08 22:27 ` Brian F. G. Bidulock
2002-10-08 23:39 ` David S. Miller
2002-10-08 23:18 ` David S. Miller
2002-10-09 0:21 ` Brian F. G. Bidulock
2002-10-09 0:00 ` Robert Love
[not found] ` <mailman.1034119380.19047.linux-kernel2news@redhat.com>
2002-10-09 0:30 ` Pete Zaitcev [this message]
2002-10-09 0:40 ` Brian F. G. Bidulock
2002-10-09 12:20 Petr Vandrovec
2002-10-09 19:54 ` Brian F. G. Bidulock
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=200210090030.g990UTe08202@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=bidulock@openss7.org \
--cc=linux-kernel@vger.kernel.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