public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Namhyung Kim <namhyung@gmail.com>
Cc: kgdb-bugreport@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Kgdb-bugreport] [PATCH] kdb: add usage string of 'per_cpu' command
Date: Fri, 25 Mar 2011 15:37:54 -0500	[thread overview]
Message-ID: <4D8CFD22.6070709@windriver.com> (raw)
In-Reply-To: <1299067738-25680-1-git-send-email-namhyung@gmail.com>

On 03/02/2011 06:08 AM, Namhyung Kim wrote:
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> ---
>  kernel/debug/kdb/kdb_main.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c
> index bd3e8e29caa3..2486021ff5d9 100644
> --- a/kernel/debug/kdb/kdb_main.c
> +++ b/kernel/debug/kdb/kdb_main.c
> @@ -2892,7 +2892,7 @@ static void __init kdb_inittab(void)
>  	  "Send a signal to a process", 0, KDB_REPEAT_NONE);
>  	kdb_register_repeat("summary", kdb_summary, "",
>  	  "Summarize the system", 4, KDB_REPEAT_NONE);
> -	kdb_register_repeat("per_cpu", kdb_per_cpu, "",
> +	kdb_register_repeat("per_cpu", kdb_per_cpu, "<sym> [<bytes>] [<cpu>]",
>  	  "Display per_cpu variables", 3, KDB_REPEAT_NONE);
>  	kdb_register_repeat("grephelp", kdb_grep_help, "",
>  	  "Display help on | grep", 0, KDB_REPEAT_NONE);


Thanks,

I added this to the queued patches.

Jason.

      reply	other threads:[~2011-03-25 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 12:08 [PATCH] kdb: add usage string of 'per_cpu' command Namhyung Kim
2011-03-25 20:37 ` Jason Wessel [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=4D8CFD22.6070709@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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