[PATCH] docs: spi: spi-master: use literal blocks for commands

[PATCH] docs: spi: spi-master: use literal blocks for commands

[Randy Dunlap]

Use literal blocks for console I/O to separate it from the
surrounding text. Otherwise the lines run together, without any
clear break before or after the commands.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
Cc: Vishwaroop A <va@nvidia.com>
Cc: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org

 Documentation/ABI/testing/sysfs-class-spi-master |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

--- linux-next-20260918.orig/Documentation/ABI/testing/sysfs-class-spi-master
+++ linux-next-20260918/Documentation/ABI/testing/sysfs-class-spi-master
@@ -17,7 +17,8 @@ Description:	(WO) Instantiate a new SPI
 		with delete_device; platform and DT devices are not
 		affected.
 
-		Example:
+		Example::
+
 		# echo spidev 0 > /sys/class/spi_master/spi0/new_device
 		# echo spidev 0 10000000 > /sys/class/spi_master/spi0/new_device
 		# echo spidev 0 10000000 3 > /sys/class/spi_master/spi0/new_device
@@ -30,5 +31,6 @@ Description:	(WO) Remove a SPI device pr
 		new_device. Takes a single parameter: the chip select
 		number of the device to remove.
 
-		Example:
+		Example::
+
 		# echo 0 > /sys/class/spi_master/spi0/delete_device

Re: [PATCH] docs: spi: spi-master: use literal blocks for commands

[Mark Brown]

On Sun, 20 Sep 2026 21:47:13 -0700, Randy Dunlap wrote:
> docs: spi: spi-master: use literal blocks for commands

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.4

Thanks!

[1/1] docs: spi: spi-master: use literal blocks for commands
      https://git.kernel.org/broonie/spi/c/3c82e199d411

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark