From: Ian Rogers <irogers@google.com>
To: Alejandro Colomar <alx@kernel.org>,
"G . Branden Robinson" <g.branden.robinson@gmail.com>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Jonathan Corbet <corbet@lwn.net>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
Ian Rogers <irogers@google.com>
Subject: [PATCH v5 3/4] proc_pid_fdinfo.5: Add subsection headers for different fd types
Date: Thu, 5 Dec 2024 23:38:27 -0800 [thread overview]
Message-ID: <20241206073828.1119464-3-irogers@google.com> (raw)
In-Reply-To: <20241206073828.1119464-1-irogers@google.com>
Make the sections about eventfd, epoll, signalfd, inotify, fanotify,
timerfd better separated with a clearer subsection header.
---
man/man5/proc_pid_fdinfo.5 | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/man/man5/proc_pid_fdinfo.5 b/man/man5/proc_pid_fdinfo.5
index 2797ae216..c4914f1f3 100644
--- a/man/man5/proc_pid_fdinfo.5
+++ b/man/man5/proc_pid_fdinfo.5
@@ -57,6 +57,7 @@ is the ID of the mount containing this file.
See the description of
.IR /proc/ pid /mountinfo .
.RE
+.SS eventfd
.P
For eventfd file descriptors (see
.BR eventfd (2)),
@@ -75,6 +76,7 @@ eventfd\-count: 40
.P
.I eventfd\-count
is the current value of the eventfd counter, in hexadecimal.
+.SS epoll
.P
For epoll file descriptors (see
.BR epoll (7)),
@@ -108,6 +110,7 @@ descriptor.
The
.I data
field is the data value associated with this file descriptor.
+.SS signalfd
.P
For signalfd file descriptors (see
.BR signalfd (2)),
@@ -133,6 +136,7 @@ and
.BR SIGQUIT ;
see
.BR signal (7).)
+.SS inotify
.P
For inotify file descriptors (see
.BR inotify (7)),
@@ -173,6 +177,7 @@ file is exposed as a file handle, via three hexadecimal fields:
.IR fhandle\-type ,
and
.IR f_handle .
+.SS fanotify
.P
For fanotify file descriptors (see
.BR fanotify (7)),
@@ -229,6 +234,7 @@ The mask of events that are ignored for this mark
.P
For details on these fields, see
.BR fanotify_mark (2).
+.SS timerfd
.P
For timerfd file descriptors (see
.BR timerfd (2)),
--
2.47.0.338.g60cca15819-goog
next prev parent reply other threads:[~2024-12-06 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 7:38 [PATCH v5 1/4] proc_pid_fdinfo.5: Reduce indent for most of the page Ian Rogers
2024-12-06 7:38 ` [PATCH v5 2/4] proc_pid_fdinfo.5: Make pid clearer in the name and 1st paragraph Ian Rogers
2024-12-06 15:19 ` Alejandro Colomar
2024-12-06 7:38 ` Ian Rogers [this message]
2024-12-06 15:20 ` [PATCH v5 3/4] proc_pid_fdinfo.5: Add subsection headers for different fd types Alejandro Colomar
2024-12-06 7:38 ` [PATCH v5 4/4] proc_pid_fdinfo.5: Add DRM subsection Ian Rogers
2024-12-06 15:16 ` [PATCH v5 1/4] proc_pid_fdinfo.5: Reduce indent for most of the page Alejandro Colomar
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=20241206073828.1119464-3-irogers@google.com \
--to=irogers@google.com \
--cc=airlied@gmail.com \
--cc=alx@kernel.org \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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