From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PULL v2 00/22] Docker and block patches
Date: Fri, 2 Jun 2017 19:49:45 +0800 [thread overview]
Message-ID: <20170602114945.GG2120@lemon.lan> (raw)
In-Reply-To: <149640353153.4078.12133676529633625501@f98a8425f76e>
On Fri, 06/02 04:38, no-reply@patchew.org wrote:
> Checking PATCH 14/22: util: add stats64 module...
> ERROR: memory barrier without comment
> #332: FILE: util/stats64.c:102:
> + smp_wmb();
>
> ERROR: memory barrier without comment
> #361: FILE: util/stats64.c:131:
> + smp_wmb();
>
> total: 2 errors, 0 warnings, 335 lines checked
As explained by Paolo in v1, the comments are just one more line above so it's a
false positive.
Fam
next prev parent reply other threads:[~2017-06-02 11:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 8:10 [Qemu-devel] [PULL v2 00/22] Docker and block patches Fam Zheng
2017-06-02 8:10 ` [Qemu-devel] [PULL v2 01/22] docker: Run tests with current user Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 02/22] docker: Add bzip2 and hostname to fedora image Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 03/22] docker: Add libaio " Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 04/22] docker: Add flex and bison to centos6 image Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 05/22] block: access copy_on_read with atomic ops Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 06/22] block: access quiesce_counter " Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 07/22] block: access io_limits_disabled " Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 08/22] block: access serialising_in_flight " Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 09/22] block: access wakeup " Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 10/22] block: access io_plugged " Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 11/22] throttle-groups: only start one coroutine from drained_begin Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 12/22] throttle-groups: do not use qemu_co_enter_next Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 13/22] throttle-groups: protect throttled requests with a CoMutex Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 14/22] util: add stats64 module Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 15/22] block: use Stat64 for wr_highest_offset Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 16/22] block: access write_gen with atomics Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 17/22] block: protect tracked_requests and flush_queue with reqs_lock Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 18/22] block: introduce dirty_bitmap_mutex Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 19/22] migration/block: reset dirty bitmap before reading Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 20/22] block: protect modification of dirty bitmaps with a mutex Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 21/22] block: introduce block_account_one_io Fam Zheng
2017-06-02 8:11 ` [Qemu-devel] [PULL v2 22/22] block: make accounting thread-safe Fam Zheng
2017-06-02 11:38 ` [Qemu-devel] [PULL v2 00/22] Docker and block patches no-reply
2017-06-02 11:49 ` Fam Zheng [this message]
2017-06-02 15:50 ` Peter Maydell
2017-06-02 21:30 ` Fam Zheng
2017-06-05 10:43 ` Paolo Bonzini
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=20170602114945.GG2120@lemon.lan \
--to=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.