From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "David S. Miller" <davem@redhat.com>
Cc: shirsch@adelphia.net, linux-kernel@vger.kernel.org
Subject: Re: Adaptec AIC7XXX v 6.0.6 BETA Released
Date: Wed, 13 Dec 2000 21:57:23 -0700 [thread overview]
Message-ID: <200012140457.eBE4vNs43248@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Wed, 13 Dec 2000 20:22:48 PST." <200012140422.UAA10340@pizda.ninka.net>
> Date: Wed, 13 Dec 2000 20:56:08 -0700
> From: "Justin T. Gibbs" <gibbs@scsiguy.com>
>
> None-the-less, it seems to me that spamming the kernel namespace
> with "current" in at least the way that the 2.2 kernels do (does
> this occur in later kernels?) should be corrected.
>
>Justin, "current" is a pointer to the current thread executing on the
>current processor under Linux. It has existed since day one of the
>Linux kernel and probably will exist till the end of it's life.
>
>I'm sure the BSD kernel has some similar bogosity :-)
BSD has curproc, but that is considerably less likely to be
used in "inoccent code" than "current". I mean, "current what?".
It could be anything, current privledges, current process, current
thread, the current time...
--
Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-14 5:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 22:15 Justin T. Gibbs
2000-12-14 1:31 ` Steven N. Hirsch
2000-12-14 3:56 ` Justin T. Gibbs
2000-12-14 4:22 ` David S. Miller
2000-12-14 4:57 ` Justin T. Gibbs [this message]
2000-12-14 10:18 ` Alan Cox
2000-12-14 14:03 ` Justin T. Gibbs
2000-12-14 15:53 ` Martin Dalecki
2000-12-14 15:10 ` Justin T. Gibbs
2000-12-14 16:15 ` Martin Dalecki
2000-12-14 17:56 ` Alan Cox
2000-12-14 19:26 ` Gérard Roudier
2000-12-14 10:14 ` Alan Cox
2000-12-14 13:59 ` Justin T. Gibbs
2000-12-14 15:03 ` Steven N. Hirsch
2000-12-14 15:07 ` Justin T. Gibbs
2000-12-14 17:03 ` Matthew Jacob
2000-12-14 17:54 ` Alan Cox
2000-12-14 18:02 ` Justin T. Gibbs
2000-12-14 18:38 ` Alan Cox
2000-12-14 18:05 ` Alan Cox
2000-12-14 17:45 ` Andi Kleen
2000-12-14 18:35 ` Alan Cox
2000-12-14 12:26 ` Steven N. Hirsch
2000-12-14 10:22 ` J . A . Magallon
2000-12-14 13:45 ` Justin T. Gibbs
2000-12-14 14:13 ` J . A . Magallon
2000-12-14 15:48 ` Christoph Hellwig
2000-12-14 16:24 ` Justin T. Gibbs
2000-12-30 16:31 ` Steven N. Hirsch
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=200012140457.eBE4vNs43248@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shirsch@adelphia.net \
/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
all inboxes | Powered by JetHome®