public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>, <mst@redhat.com>,
	<cohuck@redhat.com>, <david.edmondson@oracle.com>
Cc: <virtio-dev@lists.oasis-open.org>, <sburla@marvell.com>,
	<jasowang@redhat.com>, <yishaih@nvidia.com>, <maorg@nvidia.com>,
	<shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH v7 2/4] admin: Fix section numbering
Date: Wed, 28 Jun 2023 00:10:48 +0300	[thread overview]
Message-ID: <20230627211050.1527507-3-parav@nvidia.com> (raw)
In-Reply-To: <20230627211050.1527507-1-parav@nvidia.com>

Requirements are put one additional level down. Fix it.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v4->v5:
- new patch
---
 admin.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/admin.tex b/admin.tex
index e51f9e6..fd3b97d 100644
--- a/admin.tex
+++ b/admin.tex
@@ -286,7 +286,7 @@ \subsection{Group administration commands}\label{sec:Basic Facilities of a Virti
 supporting multiple group types, the list of supported commands
 might differ between different group types.
 
-\devicenormative{\paragraph}{Group administration commands}{Basic Facilities of a Virtio Device / Device groups / Group administration commands}
+\devicenormative{\subsubsection}{Group administration commands}{Basic Facilities of a Virtio Device / Device groups / Group administration commands}
 
 The device MUST validate \field{opcode}, \field{group_type} and
 \field{group_member_id}, and if any of these has an invalid or
@@ -378,7 +378,7 @@ \subsection{Group administration commands}\label{sec:Basic Facilities of a Virti
 \field{VF Enable} refer to registers within the SR-IOV Extended
 Capability as specified by \hyperref[intro:PCIe]{[PCIe]}.
 
-\drivernormative{\paragraph}{Group administration commands}{Basic Facilities of a Virtio Device / Device groups / Group administration commands}
+\drivernormative{\subsubsection}{Group administration commands}{Basic Facilities of a Virtio Device / Device groups / Group administration commands}
 
 The driver MAY discover whether device supports a specific group type
 by issuing VIRTIO_ADMIN_CMD_LIST_QUERY with the matching
-- 
2.26.2


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  parent reply	other threads:[~2023-06-27 21:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 21:10 [virtio-dev] [PATCH v7 0/4] admin: Introduce legacy registers access using AQ Parav Pandit
2023-06-27 21:10 ` [virtio-dev] [PATCH v7 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-06-27 21:10 ` Parav Pandit [this message]
2023-06-27 21:10 ` [virtio-dev] [PATCH v7 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-06-29 19:50   ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:32     ` [virtio-dev] " Parav Pandit
2023-06-29 21:45       ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:50         ` [virtio-dev] " Parav Pandit
2023-06-29 21:56           ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 22:02             ` [virtio-dev] " Parav Pandit
2023-06-29 22:07               ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 22:10                 ` [virtio-dev] " Parav Pandit
2023-06-27 21:10 ` [virtio-dev] [PATCH v7 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-06-29 19:43   ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:28     ` [virtio-dev] " Parav Pandit
2023-06-29 19:53   ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:26     ` [virtio-dev] " Parav Pandit
2023-06-29 19:41 ` [virtio-dev] Re: [PATCH v7 0/4] admin: Introduce legacy registers access using AQ Michael S. Tsirkin
2023-06-29 21:27   ` [virtio-dev] " Parav Pandit
2023-06-29 19:57 ` [virtio-dev] " Michael S. Tsirkin
2023-06-29 21:36   ` [virtio-dev] " 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=20230627211050.1527507-3-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=david.edmondson@oracle.com \
    --cc=jasowang@redhat.com \
    --cc=maorg@nvidia.com \
    --cc=mst@redhat.com \
    --cc=sburla@marvell.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=yishaih@nvidia.com \
    /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