Linux-HyperV List
 help / color / mirror / Atom feed
From: vdso@mailbox.org
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: yunbolyu@smu.edu.sg, kexinsun@smail.nju.edu.cn,
	ratnadiraw@smu.edu.sg, xutong.ma@inria.fr,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	Long Li <longli@microsoft.com>,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [PATCH] Drivers: hv: vmbus: fix typo in function name reference
Date: Tue, 30 Dec 2025 06:18:54 -0800 (PST)	[thread overview]
Message-ID: <1647289009.63012.1767104334567@app.mailbox.org> (raw)
In-Reply-To: <20251230141414.94472-1-Julia.Lawall@inria.fr>


> On 12/30/2025 6:14 AM  Julia Lawall <julia.lawall@inria.fr> wrote:
> 
>  
> Replace cmxchg by cmpxchg.
> 
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
> 

Reviewed-by: Roman Kisel <vdso@mailbox.org>

> ---
>  drivers/hv/hyperv_vmbus.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/hv/hyperv_vmbus.h b/drivers/hv/hyperv_vmbus.h
> index b2862e0a317a..cdbc5f5c3215 100644
> --- a/drivers/hv/hyperv_vmbus.h
> +++ b/drivers/hv/hyperv_vmbus.h
> @@ -375,7 +375,7 @@ static inline void vmbus_signal_eom(struct hv_message *msg, u32 old_msg_type)
>  		return;
>  
>  	/*
> -	 * The cmxchg() above does an implicit memory barrier to
> +	 * The cmpxchg() above does an implicit memory barrier to
>  	 * ensure the write to MessageType (ie set to
>  	 * HVMSG_NONE) happens before we read the
>  	 * MessagePending and EOMing. Otherwise, the EOMing

  reply	other threads:[~2025-12-30 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 14:14 [PATCH] Drivers: hv: vmbus: fix typo in function name reference Julia Lawall
2025-12-30 14:18 ` vdso [this message]
2026-01-15  7:00   ` Wei Liu

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=1647289009.63012.1767104334567@app.mailbox.org \
    --to=vdso@mailbox.org \
    --cc=Julia.Lawall@inria.fr \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kexinsun@smail.nju.edu.cn \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longli@microsoft.com \
    --cc=ratnadiraw@smu.edu.sg \
    --cc=wei.liu@kernel.org \
    --cc=xutong.ma@inria.fr \
    --cc=yunbolyu@smu.edu.sg \
    /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