From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, vulpyne@vulpyne.net,
trivial@kernel.org, crutcher+kernel@datastacks.com
Subject: Re: [PATCH][RESEND][Trivial] Documentation: sysrq, description of 'h' slightly inaccurate
Date: Mon, 13 Aug 2007 11:48:40 -0700 [thread overview]
Message-ID: <20070813114840.2bc992e6.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200708042031.27618.jesper.juhl@gmail.com>
On Sat, 4 Aug 2007 20:31:27 +0200 Jesper Juhl wrote:
> (Resending a patch from 21 May 2007 that never got any response)
>
>
> Hello,
>
> In Documentation/sysrq.txt, the description of 'h' says that any key not
> listed *above* will generate help. That's obviously not true since all the
> keys listed below 'h' will do what they are described to do, not display
> help. So change the text so that it says that any key not listed in the
> table will generate help, which is what really happens.
>
>
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Probably due to my alphabetization of the sysrq keys.
> ---
>
> Documentation/sysrq.txt | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt
> index ba328f2..865b271 100644
> --- a/Documentation/sysrq.txt
> +++ b/Documentation/sysrq.txt
> @@ -1,6 +1,6 @@
> Linux Magic System Request Key Hacks
> Documentation for sysrq.c
> -Last update: 2007-MAR-14
> +Last update: 2007-AUG-04
>
> * What is the magic SysRq key?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> @@ -78,7 +78,7 @@ On all - write a character to /proc/sysrq-trigger. e.g.:
> 'g' - Used by kgdb on ppc and sh platforms.
>
> 'h' - Will display help (actually any other key than those listed
> - above will display help. but 'h' is easy to remember :-)
> + here will display help. but 'h' is easy to remember :-)
>
> 'i' - Send a SIGKILL to all processes, except for init.
>
>
> -
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-08-13 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 18:31 Jesper Juhl
2007-08-13 18:48 ` Randy Dunlap [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=20070813114840.2bc992e6.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=crutcher+kernel@datastacks.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=vulpyne@vulpyne.net \
/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
Powered by JetHome