From: Thomas Huth <thuth@redhat.com>
To: AlanoSong@163.com, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, berrange@redhat.com,
QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [PATCH 1/2] docs/devel: Correct typo
Date: Tue, 2 Dec 2025 20:52:06 +0100 [thread overview]
Message-ID: <8ac1b4c8-5b6d-448f-9fbc-df5254c442cf@redhat.com> (raw)
In-Reply-To: <20251202131934.17324-1-AlanoSong@163.com>
On 02/12/2025 14.19, AlanoSong@163.com wrote:
> Correct typo in atomics.rst
>
> Signed-off-by: Alano Song <AlanoSong@163.com>
> ---
> docs/devel/atomics.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/devel/atomics.rst b/docs/devel/atomics.rst
> index 95c7b77c01..ea4ede4b8c 100644
> --- a/docs/devel/atomics.rst
> +++ b/docs/devel/atomics.rst
> @@ -266,7 +266,7 @@ Splitting a loop can also be useful to reduce the number of barriers:
> | n = 0; | smp_mb_release(); |
> | for (i = 0; i < 10; i++) { | for (i = 0; i < 10; i++) |
> | qatomic_store_release(&a[i], false); | qatomic_set(&a[i], false); |
> - | smp_mb(); | smb_mb(); |
> + | smp_mb(); | smp_mb(); |
> | n += qatomic_read(&b[i]); | n = 0; |
> | } | for (i = 0; i < 10; i++) |
> | | n += qatomic_read(&b[i]); |
> @@ -283,7 +283,7 @@ as well) ``smp_wmb()``:
> | | smp_mb_release(); |
> | for (i = 0; i < 10; i++) { | for (i = 0; i < 10; i++) |
> | qatomic_store_release(&a[i], false); | qatomic_set(&a[i], false); |
> - | qatomic_store_release(&b[i], false); | smb_wmb(); |
> + | qatomic_store_release(&b[i], false); | smp_wmb(); |
> | } | for (i = 0; i < 10; i++) |
> | | qatomic_set(&b[i], false); |
> +------------------------------------------+----------------------------------+
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2025-12-02 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 13:19 [PATCH 1/2] docs/devel: Correct typo AlanoSong
2025-12-02 19:52 ` Thomas Huth [this message]
2025-12-03 12:38 ` Christian Schoenebeck
2025-12-03 13:08 ` Alex Bennée
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=8ac1b4c8-5b6d-448f-9fbc-df5254c442cf@redhat.com \
--to=thuth@redhat.com \
--cc=AlanoSong@163.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).