From: Jiri Slaby <jirislaby@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Tomas Mudrunka <tomas.mudrunka@gmail.com>
Cc: corbet@lwn.net, gregkh@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v6] /proc/sysrq-trigger: accept multiple keys at once
Date: Wed, 15 Nov 2023 11:10:31 +0100 [thread overview]
Message-ID: <670993bf-a8ef-4561-8213-6a37d0598d83@kernel.org> (raw)
In-Reply-To: <cc6ecb91-3c3a-4ca8-9123-f030f8eee31d@infradead.org>
On 14. 11. 23, 23:00, Randy Dunlap wrote:
>>> + as the behavior is undefined and might change in the future versions.
>>> + e.g.::
>>
>> Even the original was lowercase. But it should be "E.g.::", right -- Greg/Jon?
>>
>
> or Randy?
Sure, thanks for stepping in.
--
js
suse labs
next prev parent reply other threads:[~2023-11-15 10:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2023111330-headstone-pyromania-c57e@gregkh>
2023-11-14 9:35 ` [PATCH v2] /proc/sysrq-trigger: accept multiple keys at once Tomas Mudrunka
2023-11-14 9:44 ` Jiri Slaby
2023-11-14 9:49 ` [PATCH v3] " Tomas Mudrunka
2023-11-14 9:50 ` Jiri Slaby
2023-11-14 9:55 ` [PATCH v4] " Tomas Mudrunka
2023-11-14 12:14 ` Greg KH
2023-11-14 12:41 ` [PATCH v5] " Tomas Mudrunka
2023-11-14 15:12 ` [PATCH v6] " Tomas Mudrunka
2023-11-14 18:04 ` Jiri Slaby
2023-11-14 22:00 ` Randy Dunlap
2023-11-15 10:10 ` Jiri Slaby [this message]
2023-11-15 10:27 ` [PATCH v7] " Tomas Mudrunka
2023-11-15 10:29 ` [PATCH v8] " Tomas Mudrunka
2023-11-15 10:34 ` [PATCH v9] " Tomas Mudrunka
2023-11-20 7:45 ` Jiri Slaby
2023-11-20 11:14 ` [PATCH v10] " Tomas Mudrunka
2023-11-20 11:32 ` Jiri Slaby
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=670993bf-a8ef-4561-8213-6a37d0598d83@kernel.org \
--to=jirislaby@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).