From: Cornelia Huck <cohuck@redhat.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>,
virtio-dev@lists.oasis-open.org
Cc: mst@redhat.com, Jean-Philippe Brucker <jean-philippe@linaro.org>
Subject: [virtio-dev] Re: [PATCH] content: Remove duplicate paragraph
Date: Mon, 04 Oct 2021 12:56:48 +0200 [thread overview]
Message-ID: <87k0it2h3j.fsf@redhat.com> (raw)
In-Reply-To: <20210930125847.28823-1-jean-philippe@linaro.org>
On Thu, Sep 30 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"). Remove the
> duplicate paragraph.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> This applies onto "Fix copy/paste bug in PCI transport paragraph", that
> fixes both paragraph titles.
> https://lists.oasis-open.org/archives/virtio-comment/202108/msg00097.html
> ---
> content.tex | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/content.tex b/content.tex
> index 4418ac8..54f7441 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -1149,14 +1149,6 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi
>
> 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 \field{cap.id} MUST be unique for any one device instance.
> -
> \subsubsection{Vendor data capability}\label{sec:Virtio
> Transport Options / Virtio Over PCI Bus / PCI Device Layout /
> Vendor data capability}
Hm. This statement is indeed included twice, but the two are not exactly
the same. For the first paragraph, do we want to use a combination of
the two? IOW, something like
"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 BAR specified by
\field{cap.bar}."
---------------------------------------------------------------------
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-04 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 12:58 [PATCH] content: Remove duplicate paragraph Jean-Philippe Brucker
2021-10-04 9:11 ` [virtio-dev] " Stefan Hajnoczi
2021-10-04 9:17 ` Michael S. Tsirkin
2021-10-04 10:56 ` Cornelia Huck [this message]
2021-10-06 11:24 ` Jean-Philippe Brucker
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=87k0it2h3j.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=mst@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