From: sashiko-bot@kernel.org
To: "Michael Kelley" <mhkelley58@gmail.com>
Cc: linux-hyperv@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Documentation: hyperv: Update documentation for sending VMBus packets
Date: Fri, 09 Oct 2026 18:44:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-165967@kernel.org> (raw)
In-Reply-To: <20261009184056.7382-1-mhklinux@outlook.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] docs: hyperv: typo in vmbus.rst 'arrving' instead of 'arriving'
--
commit 3fd30f16ff2564a1edce678567a65e19e411e062
Author: Michael Kelley <mhkelley58@gmail.com>
Documentation: hyperv: Update documentation for sending VMBus packets
The commit updates the VMBus documentation to reflect changes in the sending
functions, specifically the removal of vmbus_sendpacket_pagebuffer(), the
addition of vmbus_sendpacket_getid(), and the updated capability of
vmbus_sendpacket_mpb_desc().
> diff --git a/Documentation/virt/hyperv/vmbus.rst b/Documentation/virt/hyperv/vmbus.rst
> index 654bb48499724..9c5b712c6e397 100644
> --- a/Documentation/virt/hyperv/vmbus.rst
> +++ b/Documentation/virt/hyperv/vmbus.rst
> @@ -141,14 +141,15 @@ Three functions exist to send VMBus channel messages:
[ ... ]
> +2. vmbus_sendpacket_getid(): Similar to vmbus_sendpacket() but returns
> + a transaction ID that is matched against a reply from the Hyper-V
> + host. Useful when the struct completion (or other rendezvous data)
> + must reside on the caller's stack. By invalidating the transaction
> + ID before exiting the function due to a timeout or other error, a
> + late arrving interrupt is assured to not trash the stack.
[Severity: Low]
This isn't a bug, but there is a typo here: "arrving" instead of "arriving".
> +3. vmbus_sendpacket_mpb_desc(): Message with one or more data ranges
> + to target. Each range consists of a single offset and length plus
> + a list of GPAs that describe a logical area of guest memory.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261009184056.7382-1-mhklinux@outlook.com?part=1
next prev parent reply other threads:[~2026-10-09 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 18:40 [PATCH v2 1/1] Documentation: hyperv: Update documentation for sending VMBus packets Michael Kelley
2026-10-09 18:44 ` sashiko-bot [this message]
2026-10-12 5:39 ` Naman Jain
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=sashiko-outbox-165967@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=mhkelley58@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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