From: Rob Landley <rob@landley.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@linux-foundation.org,
"Michael S. Tsirkin" <mst@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Why does test_bit() take a volatile addr?
Date: Sun, 22 Sep 2013 16:37:27 -0500 [thread overview]
Message-ID: <1379885847.1974.45@driftwood> (raw)
In-Reply-To: <87ioy11k8s.fsf@rustcorp.com.au> (from rusty@rustcorp.com.au on Sun Sep 15 23:08:35 2013)
On 09/15/2013 11:08:35 PM, Rusty Russell wrote:
> Predates git, does anyone remember the rationale?
Depends which git: http://landley.net/kdocs/fullhist/ :)
Rob
next prev parent reply other threads:[~2013-09-22 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 4:08 Why does test_bit() take a volatile addr? Rusty Russell
2013-09-16 6:53 ` Stephen Rothwell
2013-09-16 7:26 ` Michael S. Tsirkin
2013-09-16 8:02 ` Stephen Rothwell
2013-09-16 8:47 ` Michael S. Tsirkin
2013-09-16 8:20 ` Geert Uytterhoeven
2013-09-16 8:37 ` Michael S. Tsirkin
2013-09-16 8:40 ` Oliver Neukum
2013-09-16 8:44 ` Michael S. Tsirkin
2013-09-16 8:49 ` Oliver Neukum
2013-09-16 11:59 ` Linus Torvalds
2013-09-22 21:37 ` Rob Landley [this message]
2013-09-23 1:13 ` Rusty Russell
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=1379885847.1974.45@driftwood \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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