From: Robert Love <rml@tech9.net>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: set_current_state(); vs current->state = bla;
Date: 01 Jan 2003 16:45:59 -0500 [thread overview]
Message-ID: <1041457559.1638.2.camel@icbm> (raw)
In-Reply-To: <200301012205.13131.m.c.p@wolk-project.de>
On Wed, 2003-01-01 at 16:05, Marc-Christian Petersen wrote:
> $subject says it all. Is there _any_ reason why not to use set_current_state?
If you do not need the memory barrier... but then you can use
__set_current_state().
So, no, we should not open code this ever.
Robert Love
prev parent reply other threads:[~2003-01-01 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 21:05 set_current_state(); vs current->state = bla; Marc-Christian Petersen
2003-01-01 21:45 ` Robert Love [this message]
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=1041457559.1638.2.camel@icbm \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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