From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
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: Fri, 4 Feb 2005 09:27:44 -0500 [thread overview]
Message-ID: <d120d50005020406274bc0d847@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0502041511540.6118@scrub.home>
On Fri, 4 Feb 2005 15:13:31 +0100 (CET), Roman Zippel
<zippel@linux-m68k.org> wrote:
> Hi,
>
> On Fri, 4 Feb 2005, Vojtech Pavlik wrote:
>
> > > When I go into a menu I explore option and submenus from top to bottom.
> > > So I will see PS/2 or serial, and will go there and select what I need.
> > > Then I will see that generic input layer is also needed for keyboard
> > > and go there.
> > >
> > > If generic layer is first one I select options I think are needed I could
> > > skip over the HW I/O ports thinking that I already selected everything I
> > > need as far as keyboard/mouse goes.
> > >
> > > Does this make any sense?
> >
> > Dmitry, will you make a patch that has the port options first? If no,
> > I'll likely merge Roman's patch.
>
> I don't think that putting this first is a good idea, compare it to scsi
> or alsa, which also have the generic options first and then the lowlevel
> drivers.
>
The "generic input layer" submenu is comparable to SCSI or ALSA and
has similar menu structure with userland interfaces on top and drivers
below them. Hardware ports (serio, gameport) "live" outside of generic
input layer and are shown there so they are easier to find.
--
Dmitry
next prev parent reply other threads:[~2005-02-04 14: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
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 [this message]
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=d120d50005020406274bc0d847@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
--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