linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Zachary Amsden <zach@vmware.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 9/11] Panic delay fix
Date: 6 Feb 2007 13:27:29 +0100
Date: Tue, 6 Feb 2007 13:27:29 +0100	[thread overview]
Message-ID: <20070206122729.GC47229@muc.de> (raw)
In-Reply-To: <200702060353.l163rUmj000771@zach-dev.vmware.com>

On Mon, Feb 05, 2007 at 07:53:30PM -0800, Zachary Amsden wrote:
> Failure to use real-time delay here causes the keyboard to become demonically
> possessed in the event of a kernel crash, with wildly blinking lights and
> unpredictable behavior.  This has resulted in several injuries.

There must be a reason why it wasn't default before. Has this
reason changed?

-Andi

> 
> Signed-off-by: Zachary Amsden <zach@vmware.com>
> 
> diff -r 10fac6d484e2 drivers/input/serio/i8042.c
> --- a/drivers/input/serio/i8042.c	Tue Jan 30 16:44:54 2007 -0800
> +++ b/drivers/input/serio/i8042.c	Tue Jan 30 16:45:00 2007 -0800
> @@ -9,6 +9,7 @@
>   * under the terms of the GNU General Public License version 2 as published by
>   * the Free Software Foundation.
>   */
> +#define USE_REAL_TIME_DELAY
>  
>  #include <linux/delay.h>
>  #include <linux/module.h>

  reply	other threads:[~2007-02-06 12:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06  3:53 [PATCH 9/11] Panic delay fix Zachary Amsden
2007-02-06 12:27 ` Andi Kleen [this message]
2007-02-06 21:59   ` Zachary Amsden
2007-02-07 12:35     ` Pavel Machek
2007-02-07 20:36       ` Rusty Russell
2007-02-07 22:23         ` Zachary Amsden
2007-02-08 14:43         ` Dmitry Torokhov
2007-02-08 21:26           ` Zachary Amsden
2007-02-08 21:37             ` Dmitry Torokhov
2007-02-14 12:26         ` Pavel Machek
2007-02-14 19:47           ` Zachary Amsden
2007-02-14 12:52         ` Alan
2007-02-14 20:04           ` Zachary Amsden
2007-02-14 21:34             ` Alan
2007-02-14 21:53               ` Zachary Amsden
2007-02-15  0:33                 ` Alan
2007-02-15 10:17             ` Pavel Machek
2007-02-15 23:42               ` Zachary Amsden
2007-02-15 23:49                 ` Pavel Machek
2007-02-15 23:50                 ` Jeremy Fitzhardinge
2007-02-16  3:22                 ` Rusty Russell
2007-02-07 14:58     ` Dmitry Torokhov
2007-02-07 22:31       ` Zachary Amsden
2007-02-08  8:24         ` Andi Kleen
2007-02-08  9:08           ` Zachary Amsden
2007-02-08 13:33             ` Andi Kleen
2007-02-08 14:41               ` Dmitry Torokhov
2007-02-14 12:49             ` Alan
2007-02-14 22:51 ` Rusty Russell
2007-02-15  0:28   ` Alan
2007-02-15 13:35   ` Dmitry Torokhov

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=20070206122729.GC47229@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).