mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: jbarnes@virtuousgeek.org, eric@anholt.net, airlied@redhat.com,
	randy.dunlap@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysrq, intel_fb: fix sysrq g collision
Date: Thu, 14 May 2009 16:17:47 -0700	[thread overview]
Message-ID: <20090514161747.e8683c9e.akpm@linux-foundation.org> (raw)
In-Reply-To: <4A0CA203.7050907@windriver.com>

On Thu, 14 May 2009 17:58:11 -0500
Jason Wessel <jason.wessel@windriver.com> wrote:

> Commit 79e539453b34e35f39299a899d263b0a1f1670bd introduced a
> regression where you cannot use sysrq 'g' to enter kgdb.  The solution
> is to move the intel fb sysrq over to V for video instead of G for
> graphics.  The SMP VOYAGER code to register for the sysrq-v is not
> anywhere to be found in the mainline kernel, so the comments in the
> code were cleaned up as well.
> 
> This patch also cleans up the sysrq definitions for kgdb to make it
> generic for the kernel debugger, such that the sysrq 'g' can be used
> in the future to enter a gdbstub or another kernel debugger.
> 

I was looking at that a week or two ago.

> 
> --- a/drivers/char/sysrq.c
> +++ b/drivers/char/sysrq.c
> @@ -406,7 +406,7 @@ static struct sysrq_key_op *sysrq_key_table[36] = {
>  	&sysrq_showlocks_op,		/* d */
>  	&sysrq_term_op,			/* e */
>  	&sysrq_moom_op,			/* f */
> -	/* g: May be registered by ppc for kgdb */
> +	/* g: May be registered for the kernel debugger */

And I made the mistake of believing the comment :(

      parent reply	other threads:[~2009-05-14 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 22:58 Jason Wessel
2009-05-14 23:02 ` Jesse Barnes
2009-05-14 23:17 ` Randy Dunlap
2009-05-14 23:17 ` Andrew Morton [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=20090514161747.e8683c9e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=airlied@redhat.com \
    --cc=eric@anholt.net \
    --cc=jason.wessel@windriver.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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

all inboxes | Powered by JetHome®