public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail•com>
To: linux-doc@vger•kernel.org
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	KVM <kvm@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Bagas Sanjaya <bagasdotme@gmail•com>,
	Anup Patel <anup.patel@wdc•com>,
	Paolo Bonzini <pbonzini@redhat•com>,
	Jonathan Corbet <corbet@lwn•net>,
	Paul Walmsley <paul.walmsley@sifive•com>,
	Palmer Dabbelt <palmer@dabbelt•com>,
	Albert Ou <aou@eecs•berkeley.edu>,
	linux-kernel@vger•kernel.org, linux-riscv@lists•infradead.org
Subject: [PATCH v2] Documentation: kvm: Add missing line break in api.rst
Date: Thu,  7 Apr 2022 19:33:27 +0700	[thread overview]
Message-ID: <20220407123327.159079-1-bagasdotme@gmail.com> (raw)

Add missing line break separator between literal block and description
of KVM_EXIT_RISCV_SBI.

This fixes:
</path/to/linux>/Documentation/virt/kvm/api.rst:6118: WARNING: Literal block ends without a blank line; unexpected unindent.

Fixes: da40d85805937d ("RISC-V: KVM: Document RISC-V specific parts of KVM API")
Cc: Anup Patel <anup.patel@wdc•com>
Cc: Paolo Bonzini <pbonzini@redhat•com>
Cc: Jonathan Corbet <corbet@lwn•net>
Cc: Paul Walmsley <paul.walmsley@sifive•com>
Cc: Palmer Dabbelt <palmer@dabbelt•com>
Cc: Albert Ou <aou@eecs•berkeley.edu>
Cc: kvm@vger•kernel.org
Cc: linux-kernel@vger•kernel.org
Cc: linux-riscv@lists•infradead.org
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail•com>
---
 Changes since v1 [1]:
   - Rebased on v5.18-rc1
   - Address Fixes tag problems reported by Stephen Rothwell [2] by
     removing date and quote the original commit

 [1]: https://lore.kernel.org/linux-doc/20220403065735.23859-1-bagasdotme@gmail.com/
 [2]: https://lore.kernel.org/linux-next/20220407074844.110f9285@canb.auug.org.au/

 Documentation/virt/kvm/api.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index d13fa66004672c..85c7abc51af521 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -6190,6 +6190,7 @@ Valid values for 'type' are:
 			unsigned long args[6];
 			unsigned long ret[2];
 		} riscv_sbi;
+
 If exit reason is KVM_EXIT_RISCV_SBI then it indicates that the VCPU has
 done a SBI call which is not handled by KVM RISC-V kernel module. The details
 of the SBI call are available in 'riscv_sbi' member of kvm_run structure. The

base-commit: 3123109284176b1532874591f7c81f3837bbdc17
-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2022-04-07 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 12:33 Bagas Sanjaya [this message]
2022-04-20 12:18 ` [PATCH v2] Documentation: kvm: Add missing line break in api.rst Paolo Bonzini

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=20220407123327.159079-1-bagasdotme@gmail.com \
    --to=bagasdotme@gmail$(echo .)com \
    --cc=anup.patel@wdc$(echo .)com \
    --cc=aou@eecs$(echo .)berkeley.edu \
    --cc=corbet@lwn$(echo .)net \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-riscv@lists$(echo .)infradead.org \
    --cc=palmer@dabbelt$(echo .)com \
    --cc=paul.walmsley@sifive$(echo .)com \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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