From: Yi Yang <yang.y.yi@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: akpm@osdl.org, crutcher+kernel@datastacks.com,
linux-kernel@vger.kernel.org, mj@atrey.karlin.mff.cuni.cz,
pavel@ucw.cz, schwab@suse.de
Subject: Re: [PATCH 2.6.23] SysRq: print hotkey info while pressing undef key, try 2
Date: Thu, 18 Oct 2007 22:40:57 +0800 [thread overview]
Message-ID: <47177079.2090201@gmail.com> (raw)
In-Reply-To: <E1IiBTu-0007cr-3i@faramir.fjphome.nl>
Frans Pop 写道:
> Yi Yang wrote:
>
>> Hot Key Function Description
>> ======= ====================
>> 0 Changing Loglevel to this value
>> 1 Changing Loglevel to this value
>> 2 Changing Loglevel to this value
>> 3 Changing Loglevel to this value
>> 4 Changing Loglevel to this value
>> 5 Changing Loglevel to this value
>> 6 Changing Loglevel to this value
>> 7 Changing Loglevel to this value
>> 8 Changing Loglevel to this value
>> 9 Changing Loglevel to this value
>>
>
> Wouldn't "Change Loglevel to this value" be more consistent with other
> descriptions?
> Or maybe even "Change Kernel Loglevel to <value>"; the repeated "this
> value" seems somewhat silly.
>
I think so, too, only one line should be enough.
>
>> b Resetting
>>
>
> This is not very descriptive. Maybe "Immediate System Reboot"?
>
>
>> c Trigger a crashdump
>>
>
> Most descriptions are capitalized. So for consistency this should be
> "Trigger a Crashdump". (Although my personal preference would be to drop
> the capitalization for all descriptions.)
>
>
>> p Show Regs
>>
>
> Should "Regs" be expanded to "Registers"?
>
>
>> r Keyboard mode set to XLATE
>>
>
> For consistency: "Set Keyboard Mode to XLATE"
>
> Cheers,
> Frans Pop
>
>
These descriptions are from the callers who are from many subsystems, so
I can't change it.
next prev parent reply other threads:[~2007-10-18 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 15:22 [PATCH 2.6.23] SysRq: print hotkey info while pressing undef key, try 2 Yi Yang
2007-10-17 16:10 ` Frans Pop
2007-10-18 14:40 ` Yi Yang [this message]
2007-10-17 20:09 ` Valdis.Kletnieks
2007-10-17 22:13 ` Pavel Machek
2007-10-18 14:34 ` Yi Yang
2007-10-18 17:10 ` Pavel Machek
2007-10-24 18:04 ` Crutcher Dunnavant
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=47177079.2090201@gmail.com \
--to=yang.y.yi@gmail.com \
--cc=akpm@osdl.org \
--cc=crutcher+kernel@datastacks.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@atrey.karlin.mff.cuni.cz \
--cc=pavel@ucw.cz \
--cc=schwab@suse.de \
/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