Skip to content

Commit 6836e1f

Browse files
ouptonbonzini
authored andcommitted
Documentation: KVM: Use unordered list for pre-init VGIC registers
The intent was to create a single column table, however the markup used was actually for a header which led to docs build failures: Sphinx parallel build error: docutils.utils.SystemMessage: Documentation/virt/kvm/devices/arm-vgic-v3.rst:128: (SEVERE/4) Unexpected section title or transition. Fix the issue by converting the attempted table to an unordered list. Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Closes: https://lore.kernel.org/linux-next/20250729142217.0d4e64cd@canb.auug.org.au/ Signed-off-by: Oliver Upton <oliver.upton@linux.dev> Message-ID: <20250729152242.3232229-1-oliver.upton@linux.dev> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
1 parent 03b1198 commit 6836e1f

1 file changed

Lines changed: 2 additions & 5 deletions

File tree

Documentation/virt/kvm/devices/arm-vgic-v3.rst

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -125,11 +125,8 @@ Groups:
125125
Userspace is allowed to write the following register fields prior to
126126
initialization of the VGIC:
127127

128-
=====================
129-
GICD_IIDR.Revision
130-
GICD_TYPER2.nASSGIcap
131-
=====================
132-
128+
* GICD_IIDR.Revision
129+
* GICD_TYPER2.nASSGIcap
133130

134131
GICD_IIDR.Revision is updated when the KVM implementation is changed in a
135132
way directly observable by the guest or userspace. Userspace should read

0 commit comments

Comments
 (0)