From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-arch@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Implement atomic{, 64}_{read, write}() without volatile
Date: Sat, 18 Aug 2007 03:29:48 +0200 [thread overview]
Message-ID: <5f948fd33e0908c03c07f32ae89834a9@kernel.crashing.org> (raw)
In-Reply-To: <18116.61246.856760.243185@cargo.ozlabs.ibm.com>
>> Instead, use asm() like all other atomic operations already do.
>
>> +static __inline__ long atomic64_read(const atomic_t *v)
>
>> +static __inline__ void atomic64_set(atomic_t *v, long i)
>
> s/atomic_t/atomic64_t/ in both lines. I've edited my copy of the
> patch.
Ouch, sorry about that.
Segher
prev parent reply other threads:[~2007-08-18 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d6775e129db48371cdf86e94ddfaa1d15617bb8f.1186773842.git.segher@kernel.crashing.org>
2007-08-11 0:15 ` [PATCH] powerpc: Implement atomic{, 64}_{read, write}() without volatile Segher Boessenkool
2007-08-11 0:36 ` Paul Mackerras
2007-08-17 0:43 ` Paul Mackerras
2007-08-18 1:29 ` Segher Boessenkool [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=5f948fd33e0908c03c07f32ae89834a9@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).