From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jiri Slaby <jirislaby@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Serial <linux-serial@vger.kernel.org>
Cc: "Cengiz Can" <cengiz@kernel.wtf>,
"Tomas Mudrunka" <tomas.mudrunka@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Anselm Schüler" <mail@anselmschueler.com>
Subject: Re: [PATCH] Documentation: sysrq: Remove contradicting sentence on extra /proc/sysrq-trigger characters
Date: Wed, 15 Oct 2025 16:39:20 +0700 [thread overview]
Message-ID: <aO9ryPohDdkoFykR@archie.me> (raw)
In-Reply-To: <0cc09ea7-d4f7-4e1c-9cd0-bf310faba217@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Wed, Oct 15, 2025 at 08:18:44AM +0200, Jiri Slaby wrote:
> On 15. 10. 25, 2:11, Bagas Sanjaya wrote:
> > I guess the whole "On all" description can be rewritten like:
> >
> > Write a single character to /proc/sysrq-trigger, e.g.::
> >
> > <snipped>...
> >
> > If a string (multiple characters) is written instead, only the first character
> > is processed unless the string is prepended by an underscore, like::
> >
> > <snipped>...
>
> Some kind of, yes. So Either:
> * you write no underscore and a character -- the rest is ignored and you
> should not write more than one.
> * you prepend underscore and write more of them -- all are processed.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-15 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 11:24 [PATCH] Documentation: sysrq: Remove contradicting sentence on extra /proc/sysrq-trigger characters Bagas Sanjaya
2025-10-09 2:18 ` Randy Dunlap
2025-10-14 14:55 ` Jonathan Corbet
2025-10-14 17:57 ` Randy Dunlap
2025-10-15 0:11 ` Bagas Sanjaya
2025-10-15 6:18 ` Jiri Slaby
2025-10-15 9:39 ` Bagas Sanjaya [this message]
2025-10-16 10:17 ` Tomas Mudrunka
2025-10-16 10:47 ` Bagas Sanjaya
2025-10-16 18:51 ` Randy Dunlap
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=aO9ryPohDdkoFykR@archie.me \
--to=bagasdotme@gmail.com \
--cc=cengiz@kernel.wtf \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mail@anselmschueler.com \
--cc=rdunlap@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.