public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] New set of input patches
Date: Tue, 2 Mar 2004 14:02:12 +0100	[thread overview]
Message-ID: <20040302130212.GA1963@ucw.cz> (raw)
In-Reply-To: <200402290153.08798.dtor_core@ameritech.net>

On Sun, Feb 29, 2004 at 01:53:58AM -0500, Dmitry Torokhov wrote:

> 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.

I like them very much. Do you have a bitkeeper tree anywhere where I
could pull from, so that I don't have to apply these by hand?

> 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.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  parent reply	other threads:[~2004-03-02 13:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29  6:53 [PATCH 0/9] New set of input patches Dmitry Torokhov
2004-02-29  6:55 ` [PATCH 1/9] atkbd whitespace fixes Dmitry Torokhov
2004-02-29  6:55   ` [PATCH 2/9] atkbd bad merge Dmitry Torokhov
2004-02-29  6:56     ` [PATCH 3/9] synaptics strict/relaxed protocol checks Dmitry Torokhov
2004-02-29  6:58       ` [PATCH 4/9] psmouse whitespace fixes Dmitry Torokhov
2004-02-29  6:58         ` [PATCH 5/9] psmouse broken hardware workaround Dmitry Torokhov
2004-02-29  7:00           ` [PATCH 6/9] introduce module_param_array_named Dmitry Torokhov
2004-02-29  7:01             ` [PATCH 7/9] Move joysticks to the module_param way of handling options Dmitry Torokhov
2004-02-29  7:02               ` [PATCH 8/9] introduce __obsolete_setup Dmitry Torokhov
2004-02-29  7:03                 ` [PATCH 9/9] Document removed input options using __obsolete_setup Dmitry Torokhov
2004-03-02 13:02 ` Vojtech Pavlik [this message]
2004-03-02 17:45   ` [PATCH 0/9] New set of input patches Dmitry Torokhov
2004-03-02 23:56     ` bkbits hosting (was Re: [PATCH 0/9] New set of input patches) Andy Isaacson
  -- strict thread matches above, loose matches on Subject: below --
2004-02-29 14:57 [PATCH 0/9] New set of input patches Dmitry Torokhov
2004-05-11  6:24 Dmitry Torokhov
2004-05-11  9:01 ` 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=20040302130212.GA1963@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    /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