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: Vojtech Pavlik <vojtech@suse.cz>,
	Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PS/2 mouse rate setting
Date: Wed, 29 Oct 2003 09:30:40 +0100	[thread overview]
Message-ID: <20031029083040.GA18135@ucw.cz> (raw)
In-Reply-To: <200310290136.06439.dtor_core@ameritech.net>

On Wed, Oct 29, 2003 at 01:36:04AM -0500, Dmitry Torokhov wrote:

> On Tuesday 28 October 2003 04:47 am, Vojtech Pavlik wrote:
> > > >     I need this patch to use the scroll wheel on my Logitech mouse
> > > > with my Belkin KVM switch in 2.6. This patch was in -mm for a while
> > > > before some changes there broke the diff, and I got some mail from
> > > > people who said it was helpful.  I didn't hear about any problems.
> > > >
> > > >     Linus, will you please consider applying it?
> >
> > Plase not in this shape. I don't want yet another option to the driver.
> > Dmitry said he'll whip up a patch that with a single option can limit
> > the maximum protocol of the PS/2 mouse to either PS/2, IMPS/2 or
> > ImExPS/2, possibly more, "psmouse_proto=". That's a better solution.
> >
> 
> Here it is... New parameter psmouse_proto={bare|imps|exps}. I don't think
> we should bother with providing options for the rest of the protocols as
> these 3 are most generic ones.
> 
> I marked psmouse_noext deprecated and psmouse will emit a warning if it
> is used, if you think we can still remove it completely at this time just
> let me know.
> 
> I also changed the parameter processing to module_param as it is much
> easier.

Thanks!

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-10-29  8:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 14:02 [PATCH] PS/2 mouse rate setting Andi Kleen
2003-10-27 16:32 ` Linus Torvalds
2003-10-27 18:38   ` Andi Kleen
2003-10-27 18:56     ` Linus Torvalds
2003-10-27 19:29       ` Andi Kleen
2003-10-28  0:55         ` Vojtech Pavlik
2003-10-28  1:23           ` Linus Torvalds
2003-10-28  1:29             ` Vojtech Pavlik
2003-10-27 22:47     ` Andries Brouwer
2003-10-27 23:13       ` Linus Torvalds
2003-10-28  3:52   ` jhf
2003-10-28  3:56     ` jhf
2003-10-28  9:47       ` Vojtech Pavlik
2003-10-29  6:36         ` Dmitry Torokhov
2003-10-29  8:30           ` Vojtech Pavlik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-28 16:25 Jon Smirl
2003-10-28 17:02 ` Felipe Alfaro Solana
2003-10-28 17:13   ` Jon Smirl
     [not found] <1067372443.864.15.camel@teapot.felipe-alfaro.com>
2003-10-28 20:55 ` Jon Smirl
2003-10-28 23:12   ` Felipe Alfaro Solana
     [not found] <20031027140217.GA1065@averell.suse.lists.linux.kernel>
     [not found] ` <20031028035625.GB20145@rivenstone.net.suse.lists.linux.kernel>
     [not found]   ` <20031028094709.GA4325@ucw.cz.suse.lists.linux.kernel>
     [not found]     ` <200310290136.06439.dtor_core@ameritech.net.suse.lists.linux.kernel>
     [not found]       ` <20031029083040.GA18135@ucw.cz.suse.lists.linux.kernel>
2003-10-29 12:47         ` Andi Kleen
2003-11-18 13:52           ` 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=20031029083040.GA18135@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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