From: Josef Bacik <josef@toxicpanda.com>
To: alx@kernel.org, linux-man@vger.kernel.org, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, mszeredi@redhat.com,
kernel-team@fb.com
Subject: [PATCH v2 0/2] man-pages: add documentation for statmount/listmount
Date: Wed, 26 Jun 2024 11:56:06 -0400 [thread overview]
Message-ID: <cover.1719417184.git.josef@toxicpanda.com> (raw)
V1: https://lore.kernel.org/linux-fsdevel/cover.1719341580.git.josef@toxicpanda.com/
v1->v2:
- Dropped the statx patch as Alejandro already took it (thanks!)
- Reworked everything to use semantic newlines
- Addressed all of the comments on the statmount.2 man page
I'm still unable to run anything other than make check, and if I do `make -t
lint-c-checkpatch` and then run make check lint build it fails almost
immediately on other unrelated things, so I think I'm too dumb to know how to
check these patches before I send them. However I did my best to follow all of
the suggestions. Thanks,
Josef
Josef Bacik (2):
statmount.2: New page describing the statmount syscall
listmount.2: New page describing the listmount syscall
man/man2/listmount.2 | 114 +++++++++++++++++
man/man2/statmount.2 | 289 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 403 insertions(+)
create mode 100644 man/man2/listmount.2
create mode 100644 man/man2/statmount.2
--
2.43.0
next reply other threads:[~2024-06-26 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:56 Josef Bacik [this message]
2024-06-26 15:56 ` [PATCH v2 1/2] statmount.2: New page describing the statmount syscall Josef Bacik
2024-06-26 15:56 ` [PATCH v2 2/2] listmount.2: New page describing the listmount syscall Josef Bacik
2024-06-26 17:02 ` [PATCH v2 0/2] man-pages: add documentation for statmount/listmount Alejandro Colomar
2024-06-26 18:04 ` Josef Bacik
2024-06-26 18:41 ` Alejandro Colomar
2024-06-26 21:44 ` Josef Bacik
2024-06-26 21:50 ` Josef Bacik
2024-06-26 22:02 ` Alejandro Colomar
2024-06-26 22:06 ` Alejandro Colomar
2024-06-26 21:58 ` 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=cover.1719417184.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mszeredi@redhat.com \
/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 NNTP newsgroup(s).