From: Brijesh Singh <brijesh.singh@amd.com>
To: pbonzini@redhat.com, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
Ashish.Kalra@amd.com, Brijesh Singh <brijesh.singh@amd.com>
Subject: [PATCH 1/4] docs: kvm: fix underline too short warning for KVM_SEV_RECEIVE_START
Date: Thu, 22 Apr 2021 11:38:33 -0500 [thread overview]
Message-ID: <20210422163836.27117-2-brijesh.singh@amd.com> (raw)
In-Reply-To: <20210422163836.27117-1-brijesh.singh@amd.com>
Fixes: af43cbbf954b ("KVM: SVM: Add support for KVM_SEV_RECEIVE_START command")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
---
Documentation/virt/kvm/amd-memory-encryption.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/amd-memory-encryption.rst b/Documentation/virt/kvm/amd-memory-encryption.rst
index 907adfe60090..07f8633b61cd 100644
--- a/Documentation/virt/kvm/amd-memory-encryption.rst
+++ b/Documentation/virt/kvm/amd-memory-encryption.rst
@@ -366,7 +366,7 @@ migration can restart with a new target later.
Returns: 0 on success, -negative on error
15. KVM_SEV_RECEIVE_START
-------------------------
+--------------------------
The KVM_SEV_RECEIVE_START command is used for creating the memory encryption
context for an incoming SEV guest. To create the encryption context, the user must
--
2.17.1
next prev parent reply other threads:[~2021-04-22 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 16:38 [PATCH 0/4] Fix htmldocs warning seen after SEV migration patch merge Brijesh Singh
2021-04-22 16:38 ` Brijesh Singh [this message]
2021-04-22 16:38 ` [PATCH 2/4] docs: kvm: fix underline too sort warning for KVM_SEV_RECEIVE_UPDATE_DATA Brijesh Singh
2021-04-22 16:38 ` [PATCH 3/4] docs: kvm: fix underline too short warning for KVM_SEV_RECEIVE_FINISH Brijesh Singh
2021-04-22 16:38 ` [PATCH 4/4] docs: kvm: fix inline emphasis string warning for KVM_SEV_SEND_START Brijesh Singh
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=20210422163836.27117-2-brijesh.singh@amd.com \
--to=brijesh.singh@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sfr@canb.auug.org.au \
/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®