From: Mike Galbraith <efault@gmx.de>
To: root@chaos.analogic.com
Cc: David Woodhouse <dwmw2@infradead.org>,
Dinesh Gandhewar <dinesh_gandhewar@rediffmail.com>,
mlist-linux-kernel@nntp-server.caltech.edu
Subject: Re: volatile variable
Date: Mon, 11 Aug 2003 16:49:02 +0200 [thread overview]
Message-ID: <5.2.1.1.2.20030811163616.01983b68@pop.gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0308110944350.17240@chaos>
At 10:06 AM 8/11/2003 -0400, Richard B. Johnson wrote:
>On Mon, 11 Aug 2003, David Woodhouse wrote:
>
> > On Fri, 2003-08-01 at 12:38, Richard B. Johnson wrote:
> > > First, there are already procedures available to do just
> > > what you seem to want to do, interruptible_sleep_on() and
> > > interruptible_sleep_on_timeout(). These take care of the
> > > ugly details that can trip up compilers.
> >
> > Just in case there are people reading this who don't realise that
> > Richard is trolling -- do not ever use sleep_on() and friends. They
> > _will_ introduce bugs, and hence they _will_ be removed from the kernel
> > some time in the (hopefully not-so-distant) future.
> >
>
>The linux-2.4.20 contains 516 references to "sleep_on" in the
>`drivers` tree. This is hardly a function or macro that will
>be removed. If there are bugs, they will be fixed, not removed.
They've been declared dead since (grep 'DO NOT use them' patch*)
2.5.48. See include/linux/wait.h for details.
-Mike
next prev parent reply other threads:[~2003-08-11 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 10:57 volatile variable Dinesh Gandhewar
2003-08-01 11:38 ` Richard B. Johnson
2003-08-11 13:33 ` David Woodhouse
2003-08-11 14:06 ` Richard B. Johnson
2003-08-11 14:37 ` Jakub Jelinek
2003-08-11 14:38 ` David Woodhouse
2003-08-11 14:40 ` David Howells
2003-08-11 14:49 ` Mike Galbraith [this message]
2003-08-11 17:07 ` Robert Love
2003-08-02 14:52 Harm Verhagen
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=5.2.1.1.2.20030811163616.01983b68@pop.gmx.net \
--to=efault@gmx.de \
--cc=dinesh_gandhewar@rediffmail.com \
--cc=dwmw2@infradead.org \
--cc=mlist-linux-kernel@nntp-server.caltech.edu \
--cc=root@chaos.analogic.com \
/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;
as well as URLs for NNTP newsgroup(s).