From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>, Cindy Lu <lulu@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
virtualization@lists.linux.dev, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH -next] VDUSE: fix another doc underline warning
Date: Thu, 22 Feb 2024 22:23:41 -0800 [thread overview]
Message-ID: <20240223062341.26914-1-rdunlap@infradead.org> (raw)
Extend the underline for a heading to prevent a documentation
build warning. Also spell "reconnection" correctly.
Documentation/userspace-api/vduse.rst:236: WARNING: Title underline too short.
HOW VDUSE devices reconnectoin works
----------------
Fixes: 2b3fd606c662 ("Documentation: Add reconnect process for VDUSE")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Cindy Lu <lulu@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: virtualization@lists.linux.dev
Cc: Jonathan Corbet <corbet@lwn.net>
---
Documentation/userspace-api/vduse.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -- a/Documentation/userspace-api/vduse.rst b/Documentation/userspace-api/vduse.rst
--- a/Documentation/userspace-api/vduse.rst
+++ b/Documentation/userspace-api/vduse.rst
@@ -232,8 +232,8 @@ able to start the dataplane processing a
For more details on the uAPI, please see include/uapi/linux/vduse.h.
-HOW VDUSE devices reconnectoin works
-----------------
+HOW VDUSE devices reconnection works
+------------------------------------
0. Userspace APP checks if the device /dev/vduse/vduse_name exists.
If it does not exist, need to create the instance.goto step 1
If it does exist, it means this is a reconnect and goto step 3.
next reply other threads:[~2024-02-23 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 6:23 Randy Dunlap [this message]
2024-02-23 8:07 ` Michael S. Tsirkin
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=20240223062341.26914-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®