From: Paolo Bonzini <pbonzini@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>
Cc: mttcg@greensocs.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] docs/atomics: update comparison with Linux
Date: Wed, 25 May 2016 17:29:19 +0200 [thread overview]
Message-ID: <bac47533-78c9-0e7d-e316-280b37f829b3@redhat.com> (raw)
In-Reply-To: <20160525151525.GB4546@flamenco>
On 25/05/2016 17:15, Emilio G. Cota wrote:
>> > +
>> > + In QEMU, the second kind does not exist. Currently Linux has
>> > + atomic_fetch_or only; QEMU provides all of inc, dec, and, sub, and, or.
> Not clear whether the last 'and' is redundant or is being used as
> a conjunction. Either way it would be clearer to just remove it.
The first "and" is "add". :)
Thanks,
Paolo
prev parent reply other threads:[~2016-05-25 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 12:26 [Qemu-devel] [PATCH] docs/atomics: update comparison with Linux Paolo Bonzini
2016-05-25 15:15 ` Emilio G. Cota
2016-05-25 15:29 ` Paolo Bonzini [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=bac47533-78c9-0e7d-e316-280b37f829b3@redhat.com \
--to=pbonzini@redhat.com \
--cc=cota@braap.org \
--cc=mttcg@greensocs.com \
--cc=qemu-devel@nongnu.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).