All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Yang <yang.y.yi@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
	mj@atrey.karlin.mff.cuni.cz, pavel@atrey.karlin.mff.cuni.cz,
	crutcher+kernel@datastacks.com
Subject: Re: [PATCH 2.6.23] SysRq: print hotkey info while pressing undef key
Date: Wed, 17 Oct 2007 23:08:06 +0800	[thread overview]
Message-ID: <47162556.7020009@gmail.com> (raw)
In-Reply-To: <jewstnhwuu.fsf@sykes.suse.de>

Andreas Schwab 写道:
> Yi Yang <yang.y.yi@gmail.com> writes:
>
>   
>> For SysRq, we just can get hot key list from Documentation/sysrq.txt
>> , but in the most of cases, the user can't access it by hand on
>> using SysRq to debug, so it is better for SysRq to provide an online
>> help for the users.
>>
>> SysRq has already provided a similiar help before this patch, but it
>> is not so definite that the user doesn't know what happened and how
>> to do on pressing an undefined hot key.
>>
>> In addition, that funtion has a big loop with another big loop
>> embedded which is very inefficient, it is intended to skip some hot
>> key help info for such a function as "Changing Loglevel", just print
>> a help info for this, that is very unnecessary. In fact, the key '0'
>>  - '8' have different results the user should know.
>>
>> This patch add this online help function, it'll print thw whole hot
>> key list and corresponding function descriptions, it can print the new
>> defined hot key without any changed needed.
>>
>> The output is the below on pressing an undefined hot key:
>>
>> SysRq : <6>this hot key isn't defined.
>>     
>           ^^^
>
> This is misplaced.
>   

printk(KERN_INFO "SysRq : \n") can fix it.

>   
>> @@ -410,7 +420,7 @@ void __handle_sysrq(int key, struct tty_
>>  	spin_lock_irqsave(&sysrq_key_table_lock, flags);
>>  	orig_log_level = console_loglevel;
>>  	console_loglevel = 7;
>> -	printk(KERN_INFO "SysRq : ");
>> +	printk(KERN_INFO "\nSysRq : ");
>>     
>
> It does not make any sense to put the printk level just before the
> newline, since the newline resets it to the default level.
>   
Thank you, I'll remove \n.
> Andreas.
>
>   


  reply	other threads:[~2007-10-17 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 15:50 [PATCH 2.6.23] SysRq: print hotkey info while pressing undef key Yi Yang
2007-10-16 16:01 ` Andreas Schwab
2007-10-17 15:08   ` Yi Yang [this message]
2007-10-16 17:21 ` Pavel Machek
2007-10-17 15:15   ` Yi Yang

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=47162556.7020009@gmail.com \
    --to=yang.y.yi@gmail.com \
    --cc=akpm@osdl.org \
    --cc=crutcher+kernel@datastacks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@atrey.karlin.mff.cuni.cz \
    --cc=pavel@atrey.karlin.mff.cuni.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 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.