From: Cornelia Huck <cohuck@redhat.com>
To: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Cc: Cornelia Huck <cohuck@redhat.com>
Subject: [PATCH] PCI: fix level for vendor data capability
Date: Thu, 7 Oct 2021 13:13:06 +0200 [thread overview]
Message-ID: <20211007111306.239420-1-cohuck@redhat.com> (raw)
The normative statements for the vendor data capability need
to be at paragraph level insted of subsection level.
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
---
I plan to push this as an editorial update.
---
content.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content.tex b/content.tex
index 39fe12b8ae40..5e716721edb3 100644
--- a/content.tex
+++ b/content.tex
@@ -1189,7 +1189,7 @@ \subsubsection{Vendor data capability}\label{sec:Virtio
To make it safe for a generic driver to access the capability,
reads from this capability MUST NOT have any side effects.
-\devicenormative{\subsection}{Vendor data capability}{Virtio
+\devicenormative{\paragraph}{Vendor data capability}{Virtio
Transport Options / Virtio Over PCI Bus / PCI Device Layout /
Vendor data capability}
@@ -1206,7 +1206,7 @@ \subsubsection{Vendor data capability}\label{sec:Virtio
Reads of the Vendor data capability by the driver MUST NOT have any
side effects.
-\drivernormative{\subsection}{Vendor data capability}{Virtio
+\drivernormative{\paragraph}{Vendor data capability}{Virtio
Transport Options / Virtio Over PCI Bus / PCI Device Layout /
Vendor data capability}
--
2.31.1
next reply other threads:[~2021-10-07 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 11:13 Cornelia Huck [this message]
2021-10-08 7:56 ` [virtio] Re: [PATCH] PCI: fix level for vendor data capability 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=20211007111306.239420-1-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@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