public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: torvalds@osdl.org, vojtech@ucw.cz, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] Fix 'event field not found' message filling logs
Date: Sat, 29 Jan 2005 17:45:28 +0100	[thread overview]
Message-ID: <1107017128578@twilight.ucw.cz> (raw)
In-Reply-To: <11070171283097@twilight.ucw.cz>

You can pull this changeset from:
	bk://kernel.bkbits.net/vojtech/for-linus

===================================================================

ChangeSet@1.1977.1.3, 2005-01-29 13:09:24+01:00, vojtech@silver.ucw.cz
  input: Ignore non-LED events in hid-input hidinput_event(). This gets rid
         of the "event field not found" message caused by EV_MSC type events.
  
  Signed-off-by: Vojtech Pavlik <vojtech@suse.cz>


 hid-input.c |    3 +++
 1 files changed, 3 insertions(+)

===================================================================

diff -Nru a/drivers/usb/input/hid-input.c b/drivers/usb/input/hid-input.c
--- a/drivers/usb/input/hid-input.c	2005-01-29 17:37:11 +01:00
+++ b/drivers/usb/input/hid-input.c	2005-01-29 17:37:11 +01:00
@@ -492,6 +492,9 @@
 	if (type == EV_FF)
 		return hid_ff_event(hid, dev, type, code, value);
 
+	if (type != EV_LED)
+		return -1;
+
 	if ((offset = hid_find_field(hid, type, code, &field)) == -1) {
 		warn("event field not found");
 		return -1;


      reply	other threads:[~2005-01-29 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29 16:44 [PATCH 0/3] - Three more input fixes for 2.6.11 Vojtech Pavlik
2005-01-29 16:45 ` [PATCH 1/3] Fix MUX mode disabling Vojtech Pavlik
2005-01-29 16:45   ` [PATCH 2/3] Document the atkbd.softraw module parameter Vojtech Pavlik
2005-01-29 16:45     ` Vojtech Pavlik [this message]

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=1107017128578@twilight.ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=vojtech@ucw.cz \
    /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