From: Vojtech Pavlik <vojtech@suse.cz>
To: torvalds@osdl.org, linux-kernel@vger.kernel.org, vojtech@ucw.cz
Subject: [PATCH 0/3] - Three more input fixes for 2.6.11
Date: Sat, 29 Jan 2005 17:44:50 +0100 [thread overview]
Message-ID: <20050129164450.GA14053@ucw.cz> (raw)
Hi!
The previous set introduced one bug, mostly harmless, but pretty
annoying - the hid-input driver fills the logs with the 'event field not
found' message. I'm sorry for that, I just tested that the patch does
what it should and didn't check the logs.
The last of these three patches fixes that.
The first fixes the MUX disabling routine in i8042 to really do
something on reboot, and the second patch from Andries adds a
documentation entry for atkbd.softraw.
Please include them before 2.6.11, as the bug described above would
cause a lot of e-mails to be sent to me.
The patches are available at
bk://kernel.bkbits.net/vojtech/for-linus
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next 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 Vojtech Pavlik [this message]
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 ` [PATCH 3/3] Fix 'event field not found' message filling logs Vojtech Pavlik
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=20050129164450.GA14053@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