From: Karsten Keil <kkeil@suse.de>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 02/06] Use menuconfig objects 4 - ISDN part 2/6 (CONFIG_ISDN_I4L)
Date: Thu, 31 May 2007 18:20:13 +0200 [thread overview]
Message-ID: <20070531162013.GA31575@pingi.kke.suse.de> (raw)
In-Reply-To: <465EF4F4.1090507@imap.cc>
On Thu, May 31, 2007 at 06:16:52PM +0200, Tilman Schmidt wrote:
> Am 30.05.2007 21:38 schrieb Jan Engelhardt:
> > --- linux-2.6.22-rc3-git1.orig/drivers/isdn/Kconfig
> > +++ linux-2.6.22-rc3-git1/drivers/isdn/Kconfig
> > @@ -21,9 +21,7 @@ menuconfig ISDN
> >
> > if ISDN
> >
> > -menu "Old ISDN4Linux"
> > -
> > -config ISDN_I4L
> > +menuconfig ISDN_I4L
> > tristate "Old ISDN4Linux (obsolete)"
> > ---help---
> > This driver allows you to use an ISDN-card for networking
> > @@ -44,8 +42,6 @@ if ISDN_I4L
> > source "drivers/isdn/i4l/Kconfig"
> > endif
> >
> > -endmenu
> > -
> > comment "CAPI subsystem"
> >
>
> This results in a rather strange and inconsistent presentation in
> "make xconfig", with ISDN4Linux appearing as a subtree in the left
> pane but CAPI only visible in the right pane after selecting ISDN.
> IMHO it looks much saner like this:
>
> --- a/drivers/isdn/Kconfig
> +++ b/drivers/isdn/Kconfig
> @@ -21,8 +21,6 @@ menuconfig ISDN
>
> if ISDN
>
> -menu "Old ISDN4Linux"
> -
> config ISDN_I4L
> tristate "Old ISDN4Linux (deprecated)"
> ---help---
> @@ -44,12 +42,8 @@ if ISDN_I4L
> source "drivers/isdn/i4l/Kconfig"
> endif
>
> -endmenu
> -
> -comment "CAPI subsystem"
> -
> config ISDN_CAPI
> - tristate "CAPI2.0 support"
> + tristate "CAPI 2.0 subsystem"
> help
> This provides the CAPI (Common ISDN Application Programming
> Interface, a standard making it easy for programs to access ISDN
>
> This gives you a single entry in the left pane tree for disabling
> all of ISDN with a single click, and nicely presents all of its
> suboptions in the right pane once you select the tree entry.
>
I agree.
--
Karsten Keil
SuSE Labs
ISDN and VOIP development
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)
next prev parent reply other threads:[~2007-05-31 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705301906.l4UJ62hC002388@shell0.pdx.osdl.net>
2007-05-30 19:37 ` [PATCH 01/06] Use menuconfig objects 4 - ISDN part 1/6 (CONFIG_ISDN) Jan Engelhardt
2007-05-30 19:38 ` [PATCH 02/06] Use menuconfig objects 4 - ISDN part 2/6 (CONFIG_ISDN_I4L) Jan Engelhardt
2007-05-31 16:16 ` Tilman Schmidt
2007-05-31 16:20 ` Karsten Keil [this message]
2007-05-31 19:53 ` Jan Engelhardt
2007-05-31 22:06 ` Tilman Schmidt
2007-05-30 19:39 ` [PATCH 03/06] Use menuconfig objects 4 - ISDN part 3/6 (CONFIG_ISDN_DRV_GIGASET) Jan Engelhardt
2007-05-30 19:40 ` [PATCH 04/06] Use menuconfig objects 4 - ISDN part 4/6 (CONFIG_ISDN_CAPI) Jan Engelhardt
2007-05-30 19:40 ` [PATCH 05/06] Use menuconfig objects 4 - ISDN part 5/6 (CONFIG_CAPI_AVM) Jan Engelhardt
2007-05-30 19:41 ` [PATCH 06/06] Use menuconfig objects 4 - ISDN part 6/6 (CONFIG_CAPI_EICON) Jan Engelhardt
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=20070531162013.GA31575@pingi.kke.suse.de \
--to=kkeil@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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
all inboxes | Powered by JetHome®