mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 4/4] docs: kvm: fix inline emphasis string warning for KVM_SEV_SEND_START
Date: Thu, 22 Apr 2021 11:38:36 -0500	[thread overview]
Message-ID: <20210422163836.27117-5-brijesh.singh@amd.com> (raw)
In-Reply-To: <20210422163836.27117-1-brijesh.singh@amd.com>

Fix the following warning seen with 'make htmldocs'

WARNING: Inline emphasis start-string without end-string

Fixes: 4cfdd47d6d95 ("KVM: SVM: Add KVM_SEV SEND_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 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/virt/kvm/amd-memory-encryption.rst b/Documentation/virt/kvm/amd-memory-encryption.rst
index eef3eff799fe..b45f2358e143 100644
--- a/Documentation/virt/kvm/amd-memory-encryption.rst
+++ b/Documentation/virt/kvm/amd-memory-encryption.rst
@@ -304,6 +304,7 @@ Parameters (in): struct kvm_sev_send_start
 Returns: 0 on success, -negative on error
 
 ::
+
         struct kvm_sev_send_start {
                 __u32 policy;                 /* guest policy */
 
-- 
2.17.1


      parent reply	other threads:[~2021-04-22 16:40 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 ` [PATCH 1/4] docs: kvm: fix underline too short warning for KVM_SEV_RECEIVE_START Brijesh Singh
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 ` Brijesh Singh [this message]

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-5-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®