From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"John Levon" <john.levon@nutanix.com>
Subject: [PULL 09/11] docs/system: unify the naming style for VirtIO devices
Date: Mon, 20 Oct 2025 11:41:47 +0100	[thread overview]
Message-ID: <20251020104149.4034124-10-alex.bennee@linaro.org> (raw)
In-Reply-To: <20251020104149.4034124-1-alex.bennee@linaro.org>
This makes the index look a little neater.
Reviewed-by: John Levon <john.levon@nutanix.com>
Message-ID: <20251016150357.876415-10-alex.bennee@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
diff --git a/docs/system/devices/virtio/virtio-gpu.rst b/docs/system/devices/virtio/virtio-gpu.rst
index b7eb0fc0e72..39d2fd2d21c 100644
--- a/docs/system/devices/virtio/virtio-gpu.rst
+++ b/docs/system/devices/virtio/virtio-gpu.rst
@@ -1,7 +1,7 @@
 ..
    SPDX-License-Identifier: GPL-2.0-or-later
 
-virtio-gpu
+VirtIO GPU
 ==========
 
 This document explains the setup and usage of the virtio-gpu device.
diff --git a/docs/system/devices/virtio/virtio-pmem.rst b/docs/system/devices/virtio/virtio-pmem.rst
index c82ac067315..0c24de83ec7 100644
--- a/docs/system/devices/virtio/virtio-pmem.rst
+++ b/docs/system/devices/virtio/virtio-pmem.rst
@@ -1,7 +1,5 @@
-
-===========
-virtio pmem
-===========
+VirtIO Persistent Memory
+========================
 
 This document explains the setup and usage of the virtio pmem device.
 The virtio pmem device is a paravirtualized persistent memory device
diff --git a/docs/system/devices/virtio/virtio-snd.rst b/docs/system/devices/virtio/virtio-snd.rst
index 2a9187fd701..3c797f66e03 100644
--- a/docs/system/devices/virtio/virtio-snd.rst
+++ b/docs/system/devices/virtio/virtio-snd.rst
@@ -1,4 +1,4 @@
-virtio sound
+VirtIO Sound
 ============
 
 This document explains the setup and usage of the Virtio sound device.
-- 
2.47.3
next prev parent reply	other threads:[~2025-10-20 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 10:41 [PULL 00/11] maintainer updates (gitlab, check-tcg, virtio-gpu, plugins, docs) Alex Bennée
2025-10-20 10:41 ` [PULL 01/11] gitlab: use template for ubuntu-24.04-aarch64 jobs Alex Bennée
2025-10-20 10:41 ` [PULL 02/11] gitlab: drop aarch32 runner and associated bits Alex Bennée
2025-10-20 10:41 ` [PULL 03/11] tests/tcg/multiarch/linux/linux-test: Don't try to test atime update Alex Bennée
2025-10-20 10:41 ` [PULL 04/11] Support per-head resolutions with virtio-gpu Alex Bennée
2025-10-20 11:55   ` Markus Armbruster
2025-10-20 12:46     ` Alex Bennée
2025-10-20 10:41 ` [PULL 05/11] ui/gtk-gl-area: Remove extra draw call in refresh Alex Bennée
2025-10-20 10:41 ` [PULL 06/11] hw/display: add blob map/unmap trace events Alex Bennée
2025-10-20 10:41 ` [PULL 07/11] contrib/plugins/uftrace_symbols.py: generate debug files to map symbols to source Alex Bennée
2025-10-20 10:41 ` [PULL 08/11] docs/system: split VirtIO devices from the rest Alex Bennée
2025-10-20 10:41 ` Alex Bennée [this message]
2025-10-20 10:41 ` [PULL 10/11] docs/system: drop vhost-user-rng docs Alex Bennée
2025-10-20 10:41 ` [PULL 11/11] docs/system: merge vhost-user-input into vhost-user-contrib Alex Bennée
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=20251020104149.4034124-10-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=john.levon@nutanix.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).