public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Armin Schindler <armin@melware.de>
Cc: kkeil@suse.de, kai.germaschewski@gmx.de,
	isdn4linux@listserv.isdn4linux.de, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] ISDN_CAPI_CAPIFS related cleanups
Date: Wed, 1 Feb 2006 11:44:19 +0100	[thread overview]
Message-ID: <20060201104419.GL3986@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0602010943180.30915@phoenix.one.melware.de>

On Wed, Feb 01, 2006 at 09:43:48AM +0100, Armin Schindler wrote:
> On Tue, 31 Jan 2006, Adrian Bunk wrote:
> > This patch contains the following cleanups:
> > - move the help text to the right option
> 
> where did you move it to? I just see the removal of the help text.

I moved it from ISDN_CAPI_CAPIFS to ISDN_CAPI_CAPIFS_BOOL (diff displays 
this a bit strange).

> Armin
>...
> >  config ISDN_CAPI_CAPIFS_BOOL
> >  	bool "CAPI2.0 filesystem support"
> >  	depends on ISDN_CAPI_MIDDLEWARE && ISDN_CAPI_CAPI20
> > -
> > -config ISDN_CAPI_CAPIFS
> > -	tristate
> > -	depends on ISDN_CAPI_CAPIFS_BOOL
> > -	default ISDN_CAPI_CAPI20
> >  	help
> >  	  This option provides a special file system, similar to /dev/pts with
> >  	  device nodes for the special ttys established by using the
> >  	  middleware extension above. If you want to use pppd with
> >  	  pppdcapiplugin to dial up to your ISP, say Y here.
> >  
> > +config ISDN_CAPI_CAPIFS
> > +	tristate
> > +	depends on ISDN_CAPI_CAPIFS_BOOL
> > +	default ISDN_CAPI_CAPI20
> > +
>...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-02-01 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 21:33 [2.6 patch] ISDN_CAPI_CAPIFS related cleanups Adrian Bunk
2006-01-31 21:44 ` Marcel Holtmann
2006-02-02 21:40   ` Adrian Bunk
2006-02-02 23:57     ` Marcel Holtmann
2006-02-03  8:45       ` Armin Schindler
2006-02-03  8:53         ` Marcel Holtmann
2006-02-03 10:18           ` Armin Schindler
2006-02-03 19:57             ` Marcel Holtmann
2006-02-12 11:09               ` Carsten Paeth
2006-02-12 11:36                 ` Marcel Holtmann
2006-02-18 15:46                   ` Carsten Paeth
2006-02-01  8:43 ` Armin Schindler
2006-02-01 10:44   ` Adrian Bunk [this message]
2006-02-01 11:01     ` Armin Schindler

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=20060201104419.GL3986@stusta.de \
    --to=bunk@stusta.de \
    --cc=armin@melware.de \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=kai.germaschewski@gmx.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