LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: keyboard.c: Stop flooding dmesg with useless warnings
Date: Sun, 25 Mar 2007 11:16:04 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703251113390.21880@jikos.suse.cz> (raw)
In-Reply-To: <82e4877d0703242235r7c83a867hd4f3ec740e8627fb@mail.gmail.com>
On Sun, 25 Mar 2007, Parag Warudkar wrote:
> > > 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.
First, is there any specific kernel version where this started to happen
to you, or is this long-standing bug you have been experiencing with older
kernels too?
It would be useful if you could compile your kernel with CONFIG_HID_DEBUG
and send the output both from the time the keyboard is connected and also
when things go wild.
--
Jiri Kosina
next prev parent reply other threads:[~2007-03-25 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 3:32 Parag Warudkar
2007-03-25 3:38 ` Parag Warudkar
[not found] ` <BAY144-F24481F006CCA5D5D74D6F4DF680@phx.gbl>
2007-03-25 4:28 ` About GCC4 Optimization Linus Torvalds
2007-03-25 5:07 ` David Schwartz
2007-03-25 4:31 ` Andrew Morton
2007-03-25 5:15 ` keyboard.c: Stop flooding dmesg with useless warnings Dmitry Torokhov
2007-03-25 5:27 ` Parag Warudkar
2007-03-25 5:29 ` Dmitry Torokhov
2007-03-25 5:35 ` Parag Warudkar
2007-03-25 9:16 ` Jiri Kosina [this message]
2007-03-25 14:32 ` Parag Warudkar
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=Pine.LNX.4.64.0703251113390.21880@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=dtor@insightbb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=torvalds@linux-foundation.org \
--subject='Re: keyboard.c: Stop flooding dmesg with useless warnings' \
/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
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).