From: "Štěpán Němec" <stepnem@smrk.net>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 2/3] man/man7/pipe.7: Note kernel commit of the soft limit triggered cap increase
Date: Thu, 9 Jul 2026 17:34:21 +0200 [thread overview]
Message-ID: <20260709153422.210312-2-stepnem@smrk.net> (raw)
In-Reply-To: <20260709153422.210312-1-stepnem@smrk.net>
7543e84442d7 did reference the kernel commit in its commit
message, but the convention to include it in the man page
source as well is helpful to wider audience.
Fixes: 7543e84442d7 ("pipe.7: Document change to default pipe size when soft limit is exceeded")
Signed-off-by: Štěpán Němec <stepnem@smrk.net>
---
man/man7/pipe.7 | 1 +
1 file changed, 1 insertion(+)
diff --git a/man/man7/pipe.7 b/man/man7/pipe.7
index 8641bcf4d807..d5744c2186b8 100644
--- a/man/man7/pipe.7
+++ b/man/man7/pipe.7
@@ -229,6 +229,7 @@ .SS /proc files
So long as the total number of pages allocated to pipe buffers
for this user is at this limit,
individual pipes created by a user will be
+.\" commit 46c4c9d1beb7f5b4cec4dd90e7728720583ee348
limited to two pages
(one page before Linux 5.14),
and attempts to increase a pipe's capacity will be denied.
--
2.55.0
next prev parent reply other threads:[~2026-07-09 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 15:34 [PATCH 1/3] man/: tfix Štěpán Němec
2026-07-09 15:34 ` Štěpán Němec [this message]
2026-07-10 16:46 ` [PATCH 2/3] man/man7/pipe.7: Note kernel commit of the soft limit triggered cap increase Alejandro Colomar
2026-07-09 15:34 ` [PATCH 3/3] man/man7/landlock.7: wfix Štěpán Němec
2026-07-10 16:48 ` Alejandro Colomar
2026-07-13 11:48 ` Štěpán Němec
2026-07-10 16:44 ` [PATCH 1/3] man/: tfix Alejandro Colomar
2026-07-13 12:11 ` [PATCH] man/man2/memfd_secret.2: tfix Štěpán Němec
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=20260709153422.210312-2-stepnem@smrk.net \
--to=stepnem@smrk.net \
--cc=alx@kernel.org \
--cc=linux-man@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