linux-kernel - Re: keyboard.c: Stop flooding dmesg with useless warnings

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]

Date:	Sun, 25 Mar 2007 01:35:35 -0400
From:	"Parag Warudkar" <parag.warudkar@...il.com>
To:	"Dmitry Torokhov" <dtor@...ightbb.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, "Jiri Kosina" <jkosina@...e.cz>
Subject: Re: keyboard.c: Stop flooding dmesg with useless warnings

On 3/25/07, Dmitry Torokhov <dtor@...ightbb.com> wrote:
> On Sunday 25 March 2007 01:27, Parag Warudkar wrote:
> > >
> > > Actually the keyboard driver should not emit input events for that key code.
> > > Is this a USB keyboard?
> > >
> > > --
> > > Dmitry
> > >
> >
> > Yes this is a USB keyboard.
> >
> > Any hint as to where I should start looking to make the driver not
> > emit input event for keycode==0?
> >
>
> Was it always doing that? I'll add Jiri Kosina to the CC list as he's
> involved with HID now.
>

Something (some keypress?) triggers it (by default it doesn't happen
immediately after a boot) - but once it starts it doesn't seem to stop
printing.

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