[PATCH] docs: TPMI: use literal block for commands

Randy Dunlap posted 1 patch 1 week, 1 day ago
Documentation/ABI/testing/debugfs-tpmi |    8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
[PATCH] docs: TPMI: use literal block for commands
Posted by Randy Dunlap 1 week, 1 day ago
Use a literal block for 'echo' commands to separate them 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: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Hans de Goede <hansg@kernel.org>
Cc: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org

 Documentation/ABI/testing/debugfs-tpmi |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

--- linux-next-20260914.orig/Documentation/ABI/testing/debugfs-tpmi
+++ linux-next-20260914/Documentation/ABI/testing/debugfs-tpmi
@@ -25,9 +25,11 @@ Description:
 Allows to write at any offset. It doesn't check for Read/Write access
 as hardware will not allow to write at read-only memory. This write is
 at offset multiples of 4. The format is instance,offset,contents.
-Example:
-echo 0,0x20,0xff > mem_write
-echo 1,64,64 > mem_write
+Example::
+
+  echo 0,0x20,0xff > mem_write
+  echo 1,64,64 > mem_write
+
 Users:		Debugging, any user space test suite
 
 What:		/sys/kernel/debug/tpmi-<n>/plr/domain<n>/status
Re: [PATCH] docs: TPMI: use literal block for commands
Posted by Ilpo Järvinen 1 week, 1 day ago
On Tue, 15 Sep 2026 22:49:41 -0700, Randy Dunlap wrote:

> Use a literal block for 'echo' commands to separate them from
> the surrounding text. Otherwise the lines run together, without any
> clear break before or after the commands.

Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.

FYI [if applicable to your patch], as per Linus' policy change, also
fixes are mostly routed through for-next unless the fix is for a
commit introduced in the most recent cycle or is clearly a regression
fix.

The list of commits applied:
[1/1] docs: TPMI: use literal block for commands
      commit: db1d44f20e3858c85fa8bf55ced0e833ecf26034

--
 i.