From: Keith Owens <kaos@ocs.com.au>
To: Andi Kleen <ak@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, bgerst@didntduck.org,
haba@pdc.kth.se
Subject: Re: Size of pointers in sys_call_table?
Date: Wed, 29 Aug 2001 11:00:36 +1000 [thread overview]
Message-ID: <20334.999046836@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "28 Aug 2001 18:54:06 +0200." <oupd75gjfbl.fsf@pigdrop.muc.suse.de>
On 28 Aug 2001 18:54:06 +0200,
Andi Kleen <ak@suse.de> wrote:
>[Introducing quiescent states in module unloading would probably fix that,
>as it has been discussed for a long time now, but I lost hope that it'll ever
>get implemented in the main kernel]
It will, in 2.5.
next prev parent reply other threads:[~2001-08-29 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B8B9C00.4842710D@didntduck.org.suse.lists.linux.kernel>
[not found] ` <E15blYK-0006Fb-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-08-28 16:54 ` Size of pointers in sys_call_table? Andi Kleen
2001-08-29 1:00 ` Keith Owens [this message]
2001-08-28 12:53 Harald Barth
2001-08-28 13:26 ` Brian Gerst
2001-08-28 14:30 ` Harald Barth
2001-08-28 16:17 ` Alan Cox
2001-08-29 0:49 ` Keith Owens
2001-08-29 23:26 ` 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=20334.999046836@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bgerst@didntduck.org \
--cc=haba@pdc.kth.se \
--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