From: Cornelia Huck <cohuck@redhat.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>,
virtio-dev@lists.oasis-open.org
Cc: mst@redhat.com, stefanha@redhat.com,
Jean-Philippe Brucker <jean-philippe@linaro.org>
Subject: [virtio-dev] Re: [PATCH v2] content: Remove duplicate paragraph
Date: Thu, 07 Oct 2021 10:43:07 +0200 [thread overview]
Message-ID: <87ee8xz0mc.fsf@redhat.com> (raw)
In-Reply-To: <20211006112816.71892-1-jean-philippe@linaro.org>
On Wed, Oct 06 2021, Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
> It looks like commit 356aeeb40d7a ("content: add vendor specific cfg
> type") had a merge issue. It includes the device normative paragraph for
> Shared memory capability, which was already added right above it by
> commit 855ad7af2bd6 ("shared memory: Define PCI capability").
>
> The two paragraphs differ, and the first paragraph is correct. It refers
> to struct virtio_pci_cap64 which embeds struct virtio_pci_cap:
>
> struct virtio_pci_cap64 {
> struct virtio_pci_cap {
> ...
> le32 offset;
> le32 length;
> } cap;
> u32 offset_hi;
> u32 length_hi;
> }
>
> Merge the two paragraph while keeping the best of both. Drop the spaces
> after \field to stay consistent with the rest of the document.
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> v1: https://www.mail-archive.com/virtio-dev@lists.oasis-open.org/msg07815.html
> ---
> content.tex | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
> diff --git a/content.tex b/content.tex
> index 288e62f..39fe12b 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -1143,17 +1143,10 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi
>
> \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}
> -MUST be contained within the BAR specified by \field{cap.bar}.
> -
> -The \field{cap.id} MUST be unique for any one device instance.
> -
> -\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
> -{cap.length_hi} fields MUST be contained within the declared bar.
> +The region defined by the combination of the \field{cap.offset},
> +\field{offset_hi}, and \field{cap.length}, \field{length_hi}
> +fields MUST be contained within the BAR specified by
> +\field{cap.bar}.
>
> The \field{cap.id} MUST be unique for any one device instance.
>
LGTM; I think this is still within the scope of editorial updates.
---------------------------------------------------------------------
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:[~2021-10-07 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 11:28 [PATCH v2] content: Remove duplicate paragraph Jean-Philippe Brucker
2021-10-07 8:41 ` [virtio-dev] " Stefan Hajnoczi
2021-10-07 8:43 ` Cornelia Huck [this message]
2021-10-07 9:00 ` [virtio-dev] " Cornelia Huck
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=87ee8xz0mc.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=mst@redhat.com \
--cc=stefanha@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox