From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] Kconfig: cleanup input menu
Date: Sat, 29 Jan 2005 21:27:28 -0500 [thread overview]
Message-ID: <200501292127.29418.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0501300212170.30794@scrub.home>
On Saturday 29 January 2005 20:16, Roman Zippel wrote:
> Hi,
>
> On Sat, 29 Jan 2005, Dmitry Torokhov wrote:
>
> > > That's fine, but why is it in the input menu? How do you suggest to make
> > > it selectable without selecting input and without messing the menu
> > > structure?
> >
> > Well, probably split input into sections, one of the options would be
> > something like "Generic Input Layer" and have evdev, mousedev, etc
> > depend on it. serio will not depend on it... nor will gameport as
> > I can see someone wanting gameport_raw.
>
> That's not the point of my patch. Feel free to restructure the input menu,
> if you need help you can ask me, but is there any practically relevant
> reason, that serio_raw must not depend on INPUT right now?
>
Well, with the current Kconfig I can de-select INPUT and still select
serio and serio_raw and access my AUX port via /dev/psaux. I don't know
if anyone would really do it, but why not?
Btw, what was the point of your patch?
--
Dmitry
next prev parent reply other threads:[~2005-01-30 2:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 22:20 [PATCH 6/8] Kconfig: cleanup input menu Roman Zippel
2005-01-29 22:50 ` Dmitry Torokhov
2005-01-29 23:20 ` Roman Zippel
2005-01-29 23:40 ` Dmitry Torokhov
2005-01-29 23:56 ` Roman Zippel
2005-01-30 0:32 ` Dmitry Torokhov
2005-01-30 1:16 ` Roman Zippel
2005-01-30 2:27 ` Dmitry Torokhov [this message]
2005-01-30 3:22 ` Roman Zippel
2005-01-30 4:07 ` Dmitry Torokhov
2005-01-30 15:45 ` Roman Zippel
2005-01-30 23:39 ` Dmitry Torokhov
2005-02-04 13:14 ` Vojtech Pavlik
2005-02-04 13:51 ` Dmitry Torokhov
2005-02-04 13:58 ` Vojtech Pavlik
2005-02-04 14:13 ` Roman Zippel
2005-02-04 14:27 ` Dmitry Torokhov
2005-02-04 14:47 ` Roman Zippel
2005-02-04 14:42 ` 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=200501292127.29418.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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