From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
linux-kernel@vger.kernel.org, akpm@osdl.org, vojtech@ucw.cz
Subject: Re: [bk patches] Long delayed input update
Date: Tue, 4 Jan 2005 01:14:26 -0500 [thread overview]
Message-ID: <200501040114.26499.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0501032148210.2294@ppc970.osdl.org>
On Tuesday 04 January 2005 12:54 am, Linus Torvalds wrote:
>
> I pulled and immediately unpulled again.
>
> Vojtech, stuff like this is unacceptable:
>
> PS/2 driver library (SERIO_LIBPS2) [N/m/y/?] (NEW) ?
>
> Say Y here if you are using a driver for device connected
> to a PS/2 port, such as PS/2 mouse or standard AT keyboard.
>
> Stop messing with peoples minds. The default config should contain
> keyboard and mouse support, and unless the user asks for "Embedded" or the
> year 2010 comes along and you can't find computers with non-USB keyboards
> anyway, that's how it's going to remain.
>
> We had this _idiocy_ early in 2.5.x, and it caused untold silly problems.
> We fixed it. We're not going to re-do that mistake.
>
When I do "make oldconfig" it silently sets SERIO_LIBPS2 to Y if I have
either atkbd or psmouse built-in and if both of them are modules it gives
option [M/y]. Do you have atkbd or psmouse selected?
> Please re-do your BK tree without this. Also, considering that every
> _single_ time we've messed with the legacy keyboard/mouse controller there
> have been compatibility problems, I want to know what the advantages are.
It folds sizeable chunks of the same code from atkbd and psmouse so for ease
of maintenance.
--
Dmitry
next prev parent reply other threads:[~2005-01-04 6:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 14:28 [bk patches] Long delayed input update Vojtech Pavlik
2004-12-27 19:19 ` Dmitry Torokhov
2005-01-03 13:18 ` Vojtech Pavlik
2005-01-04 5:54 ` Linus Torvalds
2005-01-04 6:14 ` Dmitry Torokhov [this message]
2005-01-04 14:50 ` Adrian Bunk
2005-01-04 15:17 ` Dmitry Torokhov
2005-01-04 13:58 ` Vojtech Pavlik
2005-01-04 15:58 ` Linus Torvalds
2005-01-04 16:08 ` Vojtech Pavlik
2005-01-04 16:14 ` Linus Torvalds
2005-01-04 16:23 ` Dmitry Torokhov
2005-01-04 18:03 ` Linus Torvalds
2005-01-04 18:13 ` Dmitry Torokhov
2005-01-04 16:40 ` Vojtech Pavlik
2005-01-04 17:22 ` Dmitry Torokhov
2005-01-04 17:32 ` Vojtech Pavlik
2005-01-04 16:23 ` Christoph Hellwig
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=200501040114.26499.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vojtech@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).