From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com
Subject: [virtio-comment] Re: [PATCH] packed-ring: Change host,guest to device,driver
Date: Mon, 30 Oct 2023 09:41:38 +0100 [thread overview]
Message-ID: <87zg00qz7h.fsf@redhat.com> (raw)
In-Reply-To: <20231029102837-mutt-send-email-mst@kernel.org>
On Sun, Oct 29 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Sun, Oct 29, 2023 at 04:04:37PM +0200, Parav Pandit wrote:
>> Rest of the packed ring description already uses the device
>> and driver terminology. Change the introductory line as well from
>> host and guest to device and driver respectively.
>>
>> Signed-off-by: Parav Pandit <parav@nvidia.com>
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> Editorial change, right Cornelia?
Agreed.
>
>> ---
>> packed-ring.tex | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/packed-ring.tex b/packed-ring.tex
>> index 9eeb382..2bb66de 100644
>> --- a/packed-ring.tex
>> +++ b/packed-ring.tex
>> @@ -2,7 +2,7 @@ \section{Packed Virtqueues}\label{sec:Basic Facilities of a Virtio Device / Pack
>>
>> Packed virtqueues is an alternative compact virtqueue layout using
>> read-write memory, that is memory that is both read and written
>> -by both host and guest.
>> +by both the device and the driver.
>>
>> Use of packed virtqueues is negotiated by the VIRTIO_F_RING_PACKED
>> feature bit.
>> --
>> 2.34.1
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-10-30 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 14:04 [virtio-comment] [PATCH] packed-ring: Change host,guest to device,driver Parav Pandit
2023-10-29 14:28 ` [virtio-comment] " Michael S. Tsirkin
2023-10-30 8:41 ` 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=87zg00qz7h.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