markdownlint: enable rule MD032

MD032 - Lists should be surrounded by blank lines
Fixed all errors

Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com>
Change-Id: Idd18d38386c0150f5d68068a59717a34d4e1d991
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9142
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

CHANGELOG.md

@@ -173,6 +173,7 @@ Added the `nvmf_set_crdt` RPC for setting command retry delay times.
 Expanded `spdk_nvmf_poll_group_stat` with current qpair count statistics.
 
 Removed following deprecated APIs:
+
 - `spdk_nvmf_poll_group_get_stat` (function in `nvmf.h`),
 - `spdk_nvmf_transport_poll_group_get_stat` (function in `nvmf.h`),
 - `spdk_nvmf_transport_poll_group_free_stat`(function in `nvmf.h`),
@@ -405,6 +406,7 @@ use `disable-zerocopy-send-server` or `disable-zerocopy-send-client` instead.
 
 Added cmd_parser.py used to parse the args from argparse. There are
 two benefit to use command parser:
+
 - Simplify the definition of rpc method. It will reduce the rpc method code.
 - Make the rpc call more versatile. User can add private args into rpc method.
 

doc/bdevperf.md

@@ -73,6 +73,7 @@ length    | 100% of bdev size | End I/O at `offset`+`length` on the bdev
 rw        |                   | Type of I/O pattern
 
 Available rw types:
+
 - read
 - randread
 - write

mdl_rules.rb

@@ -6,7 +6,6 @@ rule 'MD013', :line_length => 170
 exclude_rule 'MD024'
 rule 'MD029', :style => "ordered"
 exclude_rule 'MD031'
-exclude_rule 'MD032'
 exclude_rule 'MD033'
 exclude_rule 'MD034'
 exclude_rule 'MD035'

test/app/fuzz/iscsi_fuzz/README.md

@@ -8,6 +8,7 @@ randomized PDU commands through a simulated iSCSI initiator.
 1. iSCSI initiator send a login request PDU to iSCSI Target. Once a session is connected,
 2. iSCSI initiator send huge amount and random PDUs continuously to iSCSI Target.
 3. iSCSI initiator send a logout request PDU to iSCSI Target in the end.
+
 Especially, iSCSI initiator need to build different bhs according to different bhs opcode.
 Then iSCSI initiator will receive all kinds of responsed opcodes from iSCSI Target.
 The application will terminate when run time expires (see the -t flag).
@@ -15,8 +16,10 @@ The application will terminate when run time expires (see the -t flag).
 ## Output
 
 By default, the fuzzer will print commands that:
+
 1. Complete successfully back from the target, or
 2. Are outstanding at the time of a connection error occurs.
+
 Commands are dumped as named objects in json format which can then be supplied back to the
 script for targeted debugging on a subsequent run.