From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v4 1/2] qemu/atomic: Update coding style to make checkpatch.pl happier
Date: Wed, 23 Sep 2020 19:27:14 +0100 [thread overview]
Message-ID: <20200923182714.GA70694@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200923151901.745277-2-philmd@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Wed, Sep 23, 2020 at 05:19:00PM +0200, Philippe Mathieu-Daudé wrote:
> To limit the number of checkpatch errors in the next commit,
> clean coding style issues first.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> False positive:
>
> ERROR: Use of volatile is usually wrong, please add a comment
> #11: FILE: include/qemu/atomic.h:328:
> +#define atomic_read__nocheck(p) (*(__typeof__(*(p)) volatile *) (p))
>
> ERROR: Use of volatile is usually wrong, please add a comment
> #12: FILE: include/qemu/atomic.h:329:
> +#define atomic_set__nocheck(p, i) ((*(__typeof__(*(p)) volatile *) (p)) = (i))
> ---
> include/qemu/atomic.h | 9 +++++----
> util/bitmap.c | 3 ++-
> util/rcu.c | 6 ++++--
> 3 files changed, 11 insertions(+), 7 deletions(-)
I already sent a pull request with the patch that renames atomic.h, but
this patch can be rebased on top:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-23 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 15:18 [PATCH v4 0/2] qemu/atomic.h: rename atomic_ to qatomic_ Philippe Mathieu-Daudé
2020-09-23 15:19 ` [PATCH v4 1/2] qemu/atomic: Update coding style to make checkpatch.pl happier Philippe Mathieu-Daudé
2020-09-23 18:27 ` Stefan Hajnoczi [this message]
2020-09-23 20:53 ` Carlo Marcelo Arenas Belón
2020-09-23 15:19 ` [PATCH v4 2/2] qemu/atomic.h: rename atomic_ to qatomic_ Philippe Mathieu-Daudé
2020-09-23 18:34 ` [PATCH v4 0/2] " no-reply
2020-09-23 22:29 ` no-reply
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=20200923182714.GA70694@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=philmd@redhat.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).