From: Sam Ravnborg <sam@ravnborg.org>
To: Karsten Keil <isdn@linux-pingi.de>, Randy Dunlap <rdunlap@xenotime.net>
Cc: David Miller <davem@davemloft.net>,
tilman@imap.cc, isdn4linux@listserv.isdn4linux.de,
i4ldeveloper@listserv.isdn4linux.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2] Documentation/isdn/INTERFACE.CAPI
Date: Wed, 22 Apr 2009 13:45:45 +0200 [thread overview]
Message-ID: <20090422114545.GA31312@uranus.ravnborg.org> (raw)
In-Reply-To: <200904221216.22740.isdn@linux-pingi.de>
On Wed, Apr 22, 2009 at 12:16:22PM +0200, Karsten Keil wrote:
> On Mittwoch, 22. April 2009 11:31:42 David Miller wrote:
> > From: Tilman Schmidt <tilman@imap.cc>
> > Date: Tue, 21 Apr 2009 11:18:52 +0200 (CEST)
> >
> > > @@ -8,6 +8,8 @@ INTERFACE
> > > - description of isdn4linux Link Level and Hardware Level interfaces.
> > > INTERFACE.fax
> > > - description of the fax subinterface of isdn4linux.
> > > +INTERFACE.CAPI
> > > + - description of kernel CAPI Link Level to Hardware Level interface.
> > > README
> > > - general info on what you need and what to do for Linux ISDN.
> > > README.FAQ
> >
> > There is no INTERFACE.fax entry in this file in the current
> > tree.
>
> Seems the file was never updated from the old CVS version.
>
> >
> > I wanted to apply this, but aparently your patch is against
> > something other than Linus's tree or net-2.6
> I will send a new signed patch after review in few hours.
>
> Thanks to Tilman for this work.
Try copying Randy on the patch - he is good at reviewing documentation.
Sam
next prev parent reply other threads:[~2009-04-22 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 19:53 [PATCH RFC] Documentation/isdn/INTERFACE.CAPI Tilman Schmidt
2009-04-21 9:18 ` [PATCH RFC v2] Documentation/isdn/INTERFACE.CAPI Tilman Schmidt
2009-04-21 9:21 ` David Miller
2009-04-22 9:31 ` David Miller
2009-04-22 10:16 ` Karsten Keil
2009-04-22 11:45 ` Sam Ravnborg [this message]
2009-04-22 11:48 ` Tilman Schmidt
2009-04-22 15:35 ` Randy Dunlap
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=20090422114545.GA31312@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davem@davemloft.net \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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