public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	kkeil@suse.de,
	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: Fri, 01 Jun 2007 00:06:04 +0200	[thread overview]
Message-ID: <465F46CC.30008@imap.cc> (raw)
In-Reply-To: <Pine.LNX.4.61.0705312152580.11140@yvahk01.tjqt.qr>

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

Am 31.05.2007 21:53 schrieb Jan Engelhardt:
> On May 31 2007 18:16, Tilman Schmidt wrote:
[...]
>> 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.
> 
> That's a gconfig/xconfig b^H missing feature.

Send patch. :-)

Anyway, treating ISDN4Linux and CAPI that differently is certainly
not appropriate, regardless of any xconfig bug, feature or other.

>> IMHO it looks much saner like this:
> 
> But then you'd still have to descend into ISDN4Linux to deactivate it.

I don't know what you mean. The only menus I have to enter first
in order to deactivate them are the ones you left alone:
"Passive cards" (ISDN_DRV_HISAX), "Active cards" (no top-level
option), "Active AVM cards" (CAPI_AVM) and "Active Eicon DIVA
Server cards" (CAPI_EICON). There's no problem deactivating
ISDN_I4L or ISDN_CAPI (or both, should the fancy take me)
directly in the ISDN menu, neither in "make xconfig" nor in
"make menuconfig".

-- 
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

  reply	other threads:[~2007-05-31 22:02 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
2007-05-31 19:53     ` Jan Engelhardt
2007-05-31 22:06       ` Tilman Schmidt [this message]
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=465F46CC.30008@imap.cc \
    --to=tilman@imap.cc \
    --cc=akpm@linux-foundation.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.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