From: David Howells <dhowells@redhat.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: David Howells <dhowells@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] a minor fix for set_mb() in Documentation/memory-barriers.txt
Date: Wed, 08 Nov 2006 11:29:10 +0000 [thread overview]
Message-ID: <11039.1162985350@redhat.com> (raw)
In-Reply-To: <20061106150329.GA226@oleg>
Oleg Nesterov <oleg@tv-sign.ru> wrote:
> set_mb() is used by set_current_state() which needs mb(), not wmb().
> I think it would be right to assume that set_mb() implies mb(), all
> arches seem to do just this.
Yes, you're right. Copy'n'paste error from the text about set_wmb() I think.
Acked-By: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2006-11-08 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 15:03 [PATCH] a minor fix for set_mb() in Documentation/memory-barriers.txt Oleg Nesterov
2006-11-08 11:29 ` David Howells [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=11039.1162985350@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.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