From: Karl Mehltretter <kmehltretter@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Yang Erkun <yangerkun@huawei.com>,
Bart Van Assche <bvanassche@acm.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] docs: sysctl: Remove obsolete sg-big-buff entry
Date: Sat, 5 Sep 2026 03:09:52 +0200 [thread overview]
Message-ID: <20260905010952.57451-1-kmehltretter@gmail.com> (raw)
The sg-big-buff sysctl no longer exists. The documented SG_BIG_BUFF
macro is only a compatibility alias and changing it does not alter the
driver default.
Fixes: 50209dec14f8 ("scsi: sg: Remove deprecated sg-big-buff")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
Documentation/admin-guide/sysctl/kernel.rst | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index b6328cd0f43e9..d9e9b12136eb2 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -1334,19 +1334,6 @@ seccomp
See Documentation/userspace-api/seccomp_filter.rst.
-sg-big-buff
-===========
-
-This file shows the size of the generic SCSI (sg) buffer.
-You can't tune it just yet, but you could change it on
-compile time by editing ``include/scsi/sg.h`` and changing
-the value of ``SG_BIG_BUFF``.
-
-There shouldn't be any reason to change this value. If
-you can come up with one, you probably know what you
-are doing anyway :)
-
-
shmall
======
--
2.53.0
next reply other threads:[~2026-09-05 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 1:09 Karl Mehltretter [this message]
2026-09-05 2:45 ` [PATCH] docs: sysctl: Remove obsolete sg-big-buff entry Randy Dunlap
2026-09-05 9:01 ` Bradley Morgan
2026-09-07 16:37 ` 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=20260905010952.57451-1-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=yangerkun@huawei.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