From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] Re: [PATCH] content.tex Fix Driver notifications label
Date: Fri, 10 Feb 2023 12:23:14 +0100 [thread overview]
Message-ID: <87k00p9331.fsf@redhat.com> (raw)
In-Reply-To: <20230203183532.90685-1-parav@nvidia.com>
On Fri, Feb 03 2023, Parav Pandit <parav@nvidia.com> wrote:
> Driver notifications section is under "Basic Facilities of a Virtio
> Device". However, the label is placed under "Virtqueues" section.
>
> Fix the label references.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> content.tex | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
Not sure if it was originally intended to sit unter the virtqueues
section (it was lifted up one level as it disappeared under the packet
ring section), might have been.
It probably makes sense to not try and move it back into the virtqueues
section, and instead do your change. Other opinions?
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-02-10 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 18:35 [PATCH] content.tex Fix Driver notifications label Parav Pandit
2023-02-10 11:23 ` Cornelia Huck [this message]
2023-02-15 5:31 ` Parav Pandit
2023-02-15 11:14 ` Michael S. Tsirkin
2023-02-15 12:19 ` [virtio-comment] " Cornelia Huck
2023-02-15 12:59 ` Michael S. Tsirkin
2023-02-15 15:08 ` [virtio-comment] " Cornelia Huck
2023-02-15 21:53 ` Parav Pandit
2023-02-16 0:20 ` Michael S. Tsirkin
2023-02-16 5:36 ` Parav Pandit
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=87k00p9331.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 \
--cc=virtio-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.