From: ralf@linux-mips.org (Ralf Baechle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/virtio: use %llu format string form atomic64_t
Date: Mon, 19 Oct 2015 11:37:00 +0200 [thread overview]
Message-ID: <20151019093700.GC2092@linux-mips.org> (raw)
In-Reply-To: <5152101.mD2bWzUJ2V@wuerfel>
On Wed, Oct 07, 2015 at 01:23:07PM +0200, Arnd Bergmann wrote:
> > I haven't checked all architectures, but I assume what happens is that
> > 64-bit ones just #define atomic64_t atomic_long_t, so they don't have
> > to provide three sets of functions.
>
> scratch that, I just looked at all the architectures and found that it's
> just completely arbitrary, even within one architecture you get a mix
> of 'long' and 'long long', plus this gem from MIPS:
>
> static __inline__ int atomic64_add_unless(atomic64_t *v, long a, long u)
>
> which truncates the result to 32 bit.
Eh... The result is 0/1 so nothing is truncated. Alpha, MIPS,
PARISC and PowerPC are using the same prototype and x86 only differs
in the use of inline instead __inline__. And anyway, that function on
MIPS is only built for CONFIG_64BIT.
What's wrong on MIPS is the comment describing the function's return value
which was changed by f24219b4e90cf70ec4a211b17fbabc725a0ddf3c (atomic: move
atomic_add_unless to generic code) and I've queued up a patch to fix that
since a few days. I guess that was a cut and paste error from
__atomic_add_unless which indeed does return the old value.
Ralf
next prev parent reply other threads:[~2015-10-19 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 10:41 [PATCH] drm/virtio: use %llu format string form atomic64_t Arnd Bergmann
2015-10-07 10:45 ` Russell King - ARM Linux
2015-10-07 11:04 ` Arnd Bergmann
2015-10-07 11:23 ` Arnd Bergmann
2015-10-19 7:34 ` Geert Uytterhoeven
2015-10-19 10:11 ` Arnd Bergmann
2015-10-19 10:39 ` Geert Uytterhoeven
2015-10-19 9:37 ` Ralf Baechle [this message]
2015-10-19 10:06 ` Arnd Bergmann
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=20151019093700.GC2092@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-arm-kernel@lists.infradead.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).