All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: sstabellini@kernel.org, anthony@xenproject.org,
	Alano Song <AlanoSong@163.com>,
	AlanoSong@163.com, QEMU Trivial <qemu-trivial@nongnu.org>,
	Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 2/2] hw/9pfs: Correct typo
Date: Wed, 03 Dec 2025 13:12:30 +0100	[thread overview]
Message-ID: <3383884.aeNJFYEL58@weasel> (raw)
In-Reply-To: <20251202132132.17636-1-AlanoSong@163.com>

On Tuesday, 2 December 2025 14:21:32 CET AlanoSong@163.com wrote:
> Correct comment typo in xen_9pfs_bh()
> 
> Signed-off-by: Alano Song <AlanoSong@163.com>

Please send a set of associated patches with a cover letter next time. It 
makes it easier for people when they are threaded together.

I assume this patch can also be pushed through qemu-trivial, so:

Reviewed-by: Christian Schoenebeck <qemu_oss@crudebyte.com>

Otherwise let me know and I'll push it through my 9p queue.

/Christian

> ---
>  hw/9pfs/xen-9p-backend.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/9pfs/xen-9p-backend.c b/hw/9pfs/xen-9p-backend.c
> index 79359d911a..ca0fff5fa9 100644
> --- a/hw/9pfs/xen-9p-backend.c
> +++ b/hw/9pfs/xen-9p-backend.c
> @@ -310,7 +310,7 @@ static void xen_9pfs_bh(void *opaque)
> 
>  again:
>      wait = ring->co != NULL && qemu_coroutine_entered(ring->co);
> -    /* paired with the smb_wmb barriers in xen_9pfs_init_in_iov_from_pdu */
> +    /* paired with the smp_wmb barriers in xen_9pfs_init_in_iov_from_pdu
> */ smp_rmb();
>      if (wait) {
>          cpu_relax();




  parent reply	other threads:[~2025-12-03 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 13:21 [PATCH 2/2] hw/9pfs: Correct typo AlanoSong
2025-12-02 19:53 ` Thomas Huth
2025-12-03 12:12 ` Christian Schoenebeck [this message]
2025-12-03 13:25   ` Alano Song

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=3383884.aeNJFYEL58@weasel \
    --to=qemu_oss@crudebyte.com \
    --cc=AlanoSong@163.com \
    --cc=anthony@xenproject.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=thuth@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.