From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/9] New set of input patches
Date: Sun, 29 Feb 2004 09:57:31 -0500 [thread overview]
Message-ID: <200402290957.31374.dtor_core@ameritech.net> (raw)
This is a resend, list seems to have eaten first copy.
Hi Vojtech,
Here is the new set of input patches that I have. You have seen some of
them, buit this time they are rediffed against 2.6.4-rc1 and in nice order.
01-atkbd-whitespace-fixes.patch
simple whitespace fixes
02-atkbd-bad-merge.patch
clean up bad merge in atkbd module (get rid of MODULE_PARMs,
atkbd_softrepeat was declared twice)
03-synaptics-relaxed-proto.patch
some hardware (PowerBook) require relaxed Synaptics protocol checks,
but relaxed checks hurt hardware implementing proper protocol when
device looses sync. With the patch synaptics driver analyzes first
full data packet and either staus in relaxed mode or switches into
strict mode.
04-psmouse-whitespace-fixes.patch
simple whitespace fixes
05-psmouse-workaround-noack.patch
some mice do not ACK "disable streaming mode" command causing psmouse
driver abort initialization without any indication to the user. This
is a regression compared to 2.4. Have kernel complain but continue
with prbing hardware (after all we got valid responce from GET ID
command).
06-module-param-array-named.patch
introduce module_param_array_named() modeled after module_param_named
that allows mapping array module option to
07-joystick-module-param.patch
complete moving input drivers to the new way of handling module
parameters using module_param()
08-obsolete-setup.patch
introduce __obsolete_setup(). This is a drop-in replacement for
__setup() for truly obsolete options. Kernel will complain when sees
such an option.
09-input-obsolete-setup.patch
document removed or renamed options in input drivers using
__obsolete_setup() so users will have some clue why old options
stopped having any effect.
--
Dmitry
next reply other threads:[~2004-02-29 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 14:57 Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 6:24 [PATCH 0/9] New set of input patches Dmitry Torokhov
2004-05-11 9:01 ` Vojtech Pavlik
2004-02-29 6:53 Dmitry Torokhov
2004-03-02 13:02 ` Vojtech Pavlik
2004-03-02 17:45 ` Dmitry Torokhov
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=200402290957.31374.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.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