public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdb: ll command won't terminate
Date: Tue, 13 Jul 2010 14:04:49 -0500	[thread overview]
Message-ID: <4C3CB8D1.4030904@windriver.com> (raw)
In-Reply-To: <E1OYkaV-0006KK-2k@eag09.americas.sgi.com>


This particular patch is already in the queue and will be in a pull
request very soon.

There are several 1-3 line regression fixes that have been found since
the kdb merge in 2.6.35.

Jason.

On 07/13/2010 01:52 PM, Cliff Wickman wrote:
>
> Hi Jason,
>
> A question, please, about a patch similar to the below that Martin Hicks
> sent, around 5/26/2010.
>
> Martin is on vacation, and suse is wondering whether the below change
> is queued for 2.6.35.  I can't find anything about it.  Could you tell me
> its status?
>
> Thanks.
>
> -Cliff
>
>
> Signed-off-by: Martin Hicks <mort@sgi.com>
> ---
>  kernel/debug/kdb/kdb_main.c |    3 +++
>  1 file changed, 3 insertions(+)
>
> Index: linux-2.6/kernel/debug/kdb/kdb_main.c
> ===================================================================
> --- linux-2.6.orig/kernel/debug/kdb/kdb_main.c
> +++ linux-2.6/kernel/debug/kdb/kdb_main.c
> @@ -2291,6 +2291,9 @@ static int kdb_ll(int argc, const char *
>  	while (va) {
>  		char buf[80];
>  
> +		if (KDB_FLAG(CMD_INTERRUPT))
> +			return 0;
> +
>  		sprintf(buf, "%s " kdb_machreg_fmt "\n", command, va);
>  		diag = kdb_parse(buf);
>  		if (diag)
>   


      reply	other threads:[~2010-07-13 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 18:52 [PATCH] kdb: ll command won't terminate Cliff Wickman
2010-07-13 19:04 ` 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=4C3CB8D1.4030904@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=cpw@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    /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