From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.oasis-open.org, mst@redhat.com
Cc: shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>
Subject: Re: [virtio-comment] [PATCH] description: Avoid splitting the wort virtqueue
Date: Fri, 17 Nov 2023 12:39:30 +0100 [thread overview]
Message-ID: <87y1ewobgt.fsf@redhat.com> (raw)
In-Reply-To: <20231029141615.1379537-1-parav@nvidia.com>
On Sun, Oct 29 2023, Parav Pandit <parav@nvidia.com> wrote:
> Don't split the word virtqueue.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> device-types/gpu/description.tex | 2 +-
> packed-ring.tex | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Thanks, applied with s/wort/word/ in the title.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2023-11-17 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 14:16 [virtio-comment] [PATCH] description: Avoid splitting the wort virtqueue Parav Pandit
2023-11-07 11:55 ` [virtio-comment] " Parav Pandit
2023-11-17 11:39 ` Cornelia Huck [this message]
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=87y1ewobgt.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.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 read-only IMAP folder(s) and NNTP newsgroup(s).