From: Cornelia Huck <cohuck@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
virtio-comment@lists.oasis-open.org, mst@redhat.com
Cc: stefanha@redhat.com, eperezma@redhat.com, oren@nvidia.com,
jasowang@redhat.com, aadam@redhat.com,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [virtio-comment] [PATCH 1/1] Fix copy/paste bug in PCI transport paragraph
Date: Mon, 04 Oct 2021 13:03:13 +0200 [thread overview]
Message-ID: <87h7dx2gsu.fsf@redhat.com> (raw)
In-Reply-To: <20210815160140.22749-1-mgurtovoy@nvidia.com>
On Sun, Aug 15 2021, Max Gurtovoy <mgurtovoy@nvidia.com> wrote:
> Refer to "Shared memory capability" and not to "Device-specific
> configuration".
>
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
> content.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/content.tex b/content.tex
> index 1bfce9f..60b6072 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -1144,7 +1144,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi
> The identifier in \field{cap.id} does not denote a certain order of
> preference; it is only used to uniquely identify a region.
>
> -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability}
> +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability}
>
> The region defined by the combination of \field{cap.offset},
> \field{offset_hi}, and \field {cap.length}, \field{length_hi}
> @@ -1152,7 +1152,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi
>
> The \field{cap.id} MUST be unique for any one device instance.
>
> -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability}
> +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability}
>
> The region defined by the combination of the \field {cap.offset},
> \field {cap.offset_hi}, and \field {cap.length}, \field
Thanks, pushed as an editorial update.
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:[~2021-10-04 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 16:01 [virtio-comment] [PATCH 1/1] Fix copy/paste bug in PCI transport paragraph Max Gurtovoy
2021-08-15 21:44 ` Michael S. Tsirkin
2021-08-16 8:10 ` Max Gurtovoy
2021-10-04 11:03 ` 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=87h7dx2gsu.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=aadam@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=oren@nvidia.com \
--cc=stefanha@redhat.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 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.