linux-kernel - Re: [PATCH] sysrq, intel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A0CA67C.30507@oracle.com>
Date:	Thu, 14 May 2009 16:17:16 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Jason Wessel <jason.wessel@...driver.com>
CC:	jbarnes@...tuousgeek.org,
	Andrew Morton <akpm@...ux-foundation.org>, eric@...olt.net,
	airlied@...hat.com, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sysrq, intel_fb: fix sysrq g collision

Jason Wessel wrote:
> This is patch is both a clean up and a regression fix because two things
> in the mainline kernel can register for sysrq-g, which is certainly a
> problem when you want to use both.
> 
> I talked to Randy and Jesse briefly about changing the intel fb video
> driver to use 'v' instead of 'g' and they agreed it would be ok to see a
> patch.  Hopefully each will ack this patch, or discuss it further.   If
> they ack the patch, I can send it on to Linus for consideration.
> 
> The long term intent here is to get mode switching with a generic kernel
> debug front end, with the short term intent to fix the sysrq collision.

Acked-by: Randy Dunlap <randy.dunlap@...cle.com>

Thanks.

-- 
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/