mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Anselm Schüler" <mail@anselmschueler.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Documentation" <linux-doc@vger.kernel.org>
Cc: Tomas Mudrunka <tomas.mudrunka@gmail.com>,
	Jiri Slaby <jirislaby@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Issue in Kernel docs / Admin Guide / SysRq
Date: Fri, 3 Oct 2025 21:26:53 +0700	[thread overview]
Message-ID: <aN_dLVPkwvxGM9R1@archie.me> (raw)
In-Reply-To: <7ca05672-dc20-413f-a923-f77ce0a9d307@anselmschueler.com>

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

On Fri, Oct 03, 2025 at 02:32:57PM +0200, Anselm Schüler wrote:
> I’m writing here because I don’t know where to find Kernel docs
> (https://docs.kernel.org/) sources and submit patches.
> 

It's in Documentation/ directory of kernel sources.

If you want to send docs patches, please read
Documentation/process/submitting-patches.rst for how to submit them and make
sure to Cc: linux-doc@vger.kernel.org.

> The page “Linux Magic System Request Key Hacks”
> (https://docs.kernel.org/admin-guide/sysrq.html) says this:
> 
> “Write a single character to /proc/sysrq-trigger. Only the first character
> is processed, the rest of the string is ignored. However, it is not
> recommended to write any extra characters as the behavior is undefined and
> might change in the future versions. E.g.:
>     echo t > /proc/sysrq-trigger”

I think that the second sentence refers to writing subsequent characters in
this context.

> 
> I interpret the command as a suggestion of how to properly use
> /proc/sysrq-trigger, and not as an example of what not to do, and I believe
> many will share this interpretation. The command as listed will write TWO
> characters to /proc/sysrq-trigger.
> 
> Either the behaviour of ignoring \n should be codified and explicitly
> supported or this section should be changed.
> 

See commit 39ff20f5fd4481 ("/proc/sysrq-trigger: accept multiple keys at
once").

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2025-10-03 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 12:32 Anselm Schüler
2025-10-03 14:12 ` Jonathan Corbet
2025-10-03 14:26 ` Bagas Sanjaya [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=aN_dLVPkwvxGM9R1@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@anselmschueler.com \
    --cc=tomas.mudrunka@gmail.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

all inboxes | Powered by JetHome®