From: Tokunori Ikegami <ikegami.t@gmail.com>
To: linux-block@vger.kernel.org
Cc: Tokunori Ikegami <ikegami.t@gmail.com>
Subject: [PATCH] docs: sysfs-block: change hidden sysfs entry listing order
Date: Sat, 6 Apr 2024 01:54:01 +0900 [thread overview]
Message-ID: <20240405165401.12637-1-ikegami.t@gmail.com> (raw)
List entries in alphabetical order.
Signed-off-by: Tokunori Ikegami <ikegami.t@gmail.com>
---
Documentation/ABI/stable/sysfs-block | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
index 1fe9a553c37b..7718ed34777e 100644
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@@ -34,6 +34,15 @@ Description:
The value type is 64 bit unsigned.
+What: /sys/block/<disk>/hidden
+Date: March 2023
+Contact: linux-block@vger.kernel.org
+Description:
+ [RO] the block device is hidden. it doesn’t produce events, and
+ can’t be opened from userspace or using blkdev_get*.
+ Used for the underlying components of multipath devices.
+
+
What: /sys/block/<disk>/inflight
Date: October 2009
Contact: Jens Axboe <axboe@kernel.dk>, Nikanth Karthikesan <knikanth@suse.de>
@@ -698,15 +707,6 @@ Description:
zoned will report "none".
-What: /sys/block/<disk>/hidden
-Date: March 2023
-Contact: linux-block@vger.kernel.org
-Description:
- [RO] the block device is hidden. it doesn’t produce events, and
- can’t be opened from userspace or using blkdev_get*.
- Used for the underlying components of multipath devices.
-
-
What: /sys/block/<disk>/stat
Date: February 2008
Contact: Jerome Marchand <jmarchan@redhat.com>
--
2.40.1
next reply other threads:[~2024-04-05 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 16:54 Tokunori Ikegami [this message]
2024-04-05 19:39 ` [PATCH] docs: sysfs-block: change hidden sysfs entry listing order Bart Van Assche
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=20240405165401.12637-1-ikegami.t@gmail.com \
--to=ikegami.t@gmail.com \
--cc=linux-block@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).