public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Subject: Re: [PATCH v2] docs: sysctl: add documentation for crypto and debug
Date: Tue, 03 Mar 2026 10:27:35 -0700	[thread overview]
Message-ID: <87seagbz7c.fsf@trenco.lwn.net> (raw)
In-Reply-To: <87ecmb5gc0.fsf@trenco.lwn.net>

Jonathan Corbet <corbet@lwn.net> writes:

> Shubham Chakraborty <chakrabortyshubham66@gmail.com> writes:
>
>> Add documentation for the /proc/sys/crypto and /proc/sys/debug
>> directories in the admin-guide. This includes tunables for FIPS
>> mode (fips_enabled, fips_name, fips_version), exception-trace,
>> and kprobes-optimization.
>>
>> The documentation is based on source code analysis and addresses
>> stylistic feedback to keep it direct and concise.
>>
>> Tested-by: Randy Dunlap <rdunlap@infradead.org>
>> Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
>> ---
>>  Documentation/admin-guide/sysctl/crypto.rst | 47 +++++++++++++++++++
>>  Documentation/admin-guide/sysctl/debug.rst  | 52 +++++++++++++++++++++
>>  Documentation/admin-guide/sysctl/index.rst  |  6 ++-
>>  3 files changed, 103 insertions(+), 2 deletions(-)
>>  create mode 100644 Documentation/admin-guide/sysctl/crypto.rst
>>  create mode 100644 Documentation/admin-guide/sysctl/debug.rst
>
> A few other comments:
>
> - This is the second v2 you have posted, which can only lead to
>   confusion.  If you only change was to add Randy's Tested-by, there is
>   no need to post a new version just for that; it will be picked up.
>
> - When posting a new version, it is good to give a quick summary of the
>   changes from the previous version, below the "---" line.
>
> - Please slow down a bit, there is no need to post multiple times in one
>   day.  Give people time to look at your work.
>
> For me, there is no need for you to post a new version unless there are
> other comments that need to be addressed.

Now applied.

Thanks,

jon

      reply	other threads:[~2026-03-03 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 20:37 [PATCH v2] docs: sysctl: add documentation for crypto and debug Shubham Chakraborty
2026-02-23 20:56 ` Jonathan Corbet
2026-03-03 17:27   ` Jonathan Corbet [this message]

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=87seagbz7c.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=chakrabortyshubham66@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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