qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Romero <gustavo.romero@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH] vhost-user: ancilliary -> ancillary
Date: Mon, 17 Nov 2025 10:44:28 -0300	[thread overview]
Message-ID: <84357dfb-8098-4d57-b144-c3019c7f6a70@linaro.org> (raw)
In-Reply-To: <44f5010964049b9988923ce1429652e0a9e8ebaf.1763380540.git.mst@redhat.com>

Hi Michael,

On 11/17/25 08:55, Michael S. Tsirkin wrote:
> My dictionary says the former spelling is incorrect.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>   docs/interop/vhost-user.rst | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst
> index 93a9c8df2b..93f756d3f4 100644
> --- a/docs/interop/vhost-user.rst
> +++ b/docs/interop/vhost-user.rst
> @@ -411,8 +411,8 @@ in the ancillary data:
>   * ``VHOST_USER_SET_INFLIGHT_FD`` (if ``VHOST_USER_PROTOCOL_F_INFLIGHT_SHMFD``)
>   * ``VHOST_USER_SET_DEVICE_STATE_FD``
>   
> -When sending file descriptors in ancilliary data, *front-end* should
> -associate the ancilliary data with a ``sendmsg`` operation (or
> +When sending file descriptors in ancillary data, *front-end* should
> +associate the ancillary data with a ``sendmsg`` operation (or
>   equivalent) that sends bytes starting with the first byte of the
>   message header.  *back-end* can therefore expect that file descriptors
>   will only be received in the first ``recvmsg`` operation for a message

Yeah, I'm not a native English speaker but in my mind the latter is the correct form :)

Reviewed-by: Gustavo Romero <gustavo.romero@linaro.org>


  reply	other threads:[~2025-11-17 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 11:55 [PATCH] vhost-user: ancilliary -> ancillary Michael S. Tsirkin
2025-11-17 13:44 ` Gustavo Romero [this message]
2025-11-17 13:59 ` Philippe Mathieu-Daudé

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=84357dfb-8098-4d57-b144-c3019c7f6a70@linaro.org \
    --to=gustavo.romero@linaro.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@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 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).