linux-kernel - Re: 2.6.19 -mm merge plans (input patches)

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: <20060920145006.05117085.akpm@osdl.org>
Date:	Wed, 20 Sep 2006 14:50:06 -0700
From:	Andrew Morton <akpm@...l.org>
To:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
Cc:	linux-kernel@...r.kernel.org, "Dave Jones" <davej@...hat.com>,
	"Marek Vasut" <marek.vasut@...il.com>
Subject: Re: 2.6.19 -mm merge plans (input patches)

On Wed, 20 Sep 2006 17:29:43 -0400
"Dmitry Torokhov" <dmitry.torokhov@...il.com> wrote:

> On 9/20/06, Andrew Morton <akpm@...l.org> wrote:
> >
> > remove-silly-messages-from-input-layer.patch
> 
> I firmly believe that we should keep reporting these conditions. This
> way we can explain why keyboard might be losing keypresses. I am open
> to changing the message text. Would "atkbd.c: keyboard reported error
> condition (FYI only)" be better? It is KERN_DEBUG after all.

But it irritates some people.

Perhaps we could make the message disable itself after the first 5-10
instances?

> > input-i8042-disable-keyboard-port-when-panicking-and-blinking.patch
> > i8042-activate-panic-blink-only-in-x.patch
> 
> There was a concern that blinking is useful even when not running X.
> Do you have any input?

No, sorry.

-
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/