From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] [patch 2.6.1] s/CONFIG_SYSRQ/CONFIG_MAGIC_SYSRQ/
Date: Sat, 17 Jan 2004 16:29:42 +0000 [thread overview]
Message-ID: <200401171729.42422.domen@coderock.org> (raw)
Hi.
Noone tested that code to see if it really works?
--- c/arch/arm/kernel/process.c 2003-12-18 03:59:37.000000000 +0100
+++ a/arch/arm/kernel/process.c 2004-01-17 16:31:02.000000000 +0100
@@ -264,7 +264,7 @@
if (!thread)
thread = ll_alloc_task_struct();
-#ifdef CONFIG_SYSRQ
+#ifdef CONFIG_MAGIC_SYSRQ
/*
* The stack must be cleared if you want SYSRQ-T to
* give sensible stack usage information
--- c/arch/um/kernel/um_arch.c 2003-12-18 03:59:18.000000000 +0100
+++ a/arch/um/kernel/um_arch.c 2004-01-17 16:31:25.000000000 +0100
@@ -376,7 +376,7 @@
static int panic_exit(struct notifier_block *self, unsigned long unused1,
void *unused2)
{
-#ifdef CONFIG_SYSRQ
+#ifdef CONFIG_MAGIC_SYSRQ
handle_sysrq('p', ¤t->thread.regs, NULL, NULL);
#endif
machine_halt();
--- c/arch/arm26/kernel/process.c 2003-12-18 03:59:35.000000000 +0100
+++ a/arch/arm26/kernel/process.c 2004-01-17 16:31:41.000000000 +0100
@@ -257,7 +257,7 @@
if (!thread)
thread = ll_alloc_task_struct();
-#ifdef CONFIG_SYSRQ
+#ifdef CONFIG_MAGIC_SYSRQ
/*
* The stack must be cleared if you want SYSRQ-T to
* give sensible stack usage information
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next reply other threads:[~2004-01-17 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 16:29 Domen Puncer [this message]
2004-01-19 1:10 ` [Kernel-janitors] [patch 2.6.1] s/CONFIG_SYSRQ/CONFIG_MAGIC_SYSRQ/ GOTO Masanori
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=200401171729.42422.domen@coderock.org \
--to=domen@coderock.org \
--cc=kernel-janitors@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 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.