From: Stephen Kitt <steve@sk2.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Stephen Kitt <steve@sk2.org>
Subject: [PATCH v2 0/5] Update the sysctl/fs documentation
Date: Fri, 30 Sep 2022 12:29:32 +0200 [thread overview]
Message-ID: <20220930102937.135841-1-steve@sk2.org> (raw)
This patch series updates the sysctl/fs in line with similar changes
made previously to sysctl/kernel and sysctl/abi:
* add an automatically-generated table of contents,
* order the entries alphabetically,
* use consistent markup.
In addition, obsolete entries are removed, and the two aio sections
are merged.
Changes since v2:
* added a cover letter
* request review from linux-fsdevel
* fix the link to core_pattern
Stephen Kitt (5):
docs: sysctl/fs: remove references to inode-max
docs: sysctl/fs: remove references to dquot-max/-nr
docs: sysctl/fs: merge the aio sections
docs: sysctl/fs: remove references to super-max/-nr
docs: sysctl/fs: re-order, prettify
Documentation/admin-guide/sysctl/fs.rst | 240 ++++++++------------
Documentation/admin-guide/sysctl/kernel.rst | 2 +
2 files changed, 97 insertions(+), 145 deletions(-)
base-commit: c3e0e1e23c70455916ff3472072437b3605c6cfe
--
2.31.1
next reply other threads:[~2022-09-30 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 10:29 Stephen Kitt [this message]
2022-09-30 10:29 ` [PATCH v2 1/5] docs: sysctl/fs: remove references to inode-max Stephen Kitt
2022-09-30 10:29 ` [PATCH v2 2/5] docs: sysctl/fs: remove references to dquot-max/-nr Stephen Kitt
2022-09-30 10:29 ` [PATCH v2 3/5] docs: sysctl/fs: merge the aio sections Stephen Kitt
2022-09-30 10:29 ` [PATCH v2 4/5] docs: sysctl/fs: remove references to super-max/-nr Stephen Kitt
2022-09-30 10:29 ` [PATCH v2 5/5] docs: sysctl/fs: re-order, prettify Stephen Kitt
2022-09-30 10:35 ` [PATCH v2 0/5] Update the sysctl/fs documentation Stephen Kitt
2022-10-19 22:43 ` 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=20220930102937.135841-1-steve@sk2.org \
--to=steve@sk2.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).