From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: [PATCH] ABI: sysfs-bus-pci: use literal blocks for commands
Date: Sun, 20 Sep 2026 21:46:37 -0700 [thread overview]
Message-ID: <20260921044637.91089-1-rdunlap@infradead.org> (raw)
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: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@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-bus-pci | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
--- linux-next-20260918.orig/Documentation/ABI/testing/sysfs-bus-pci
+++ linux-next-20260918/Documentation/ABI/testing/sysfs-bus-pci
@@ -486,19 +486,19 @@ Description:
These files provide an interface to PCIe Resizable BAR support.
A file is created for each BAR resource (N) supported by the
PCIe Resizable BAR extended capability of the device. Reading
- each file exposes the bitmap of available resource sizes:
+ each file exposes the bitmap of available resource sizes::
- # cat resource1_resize
- 00000000000001c0
+ # cat resource1_resize
+ 00000000000001c0
The bitmap represents supported resource sizes for the BAR,
where bit0 = 1MB, bit1 = 2MB, bit2 = 4MB, etc. In the above
example the device supports 64MB, 128MB, and 256MB BAR sizes.
When writing the file, the user provides the bit position of
- the desired resource size, for example:
+ the desired resource size, for example::
- # echo 7 > resource1_resize
+ # echo 7 > resource1_resize
This indicates to set the size value corresponding to bit 7,
128MB. The resulting size is 2 ^ (bit# + 20). This definition
@@ -600,7 +600,7 @@ Description:
As all DOE devices must support the DOE discovery feature,
if DOE is supported you will at least see the doe_discovery
- file, with this contents:
+ file, with this contents::
# cat doe_features/doe_discovery
0001:00
@@ -608,7 +608,7 @@ Description:
If the device supports other features you will see other
files as well. For example if CMA/SPDM and secure CMA/SPDM
are supported the doe_features directory will look like
- this:
+ this::
# ls doe_features
0001:01 0001:02 doe_discovery
next reply other threads:[~2026-09-21 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 4:46 Randy Dunlap [this message]
2026-09-26 15:39 ` Jonathan Corbet
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=20260921044637.91089-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
/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®