public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 30 Jan 2005 18:39:37 -0500	[thread overview]
Message-ID: <200501301839.37548.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0501301639171.30794@scrub.home>

On Sunday 30 January 2005 10:45, Roman Zippel wrote:
> Hi,
> 
> On Sat, 29 Jan 2005, Dmitry Torokhov wrote:
> 
> > Ok, what about making some submenus to manage number of options, like in
> > the patch below?
> 
> I'd rather move it to the bottom and the menus had no dependencies.
> Below is an alternative patch, which does a rather complete cleanup.

This one looks nice. I still think that hardware port support should go
first. My argument is:

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

  reply	other threads:[~2005-01-30 23:40 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 [this message]
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=200501301839.37548.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