From: Christoph Biedl <isdn4linux.agzq@manchmal.in-ulm.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Karsten Keil <isdn@linux-pingi.de>,
netdev@vger.kernel.org, Tilman Schmidt <tilman@imap.cc>,
Paul Bolle <pebolle@tiscali.nl>,
gigaset307x-common@lists.sourceforge.net,
isdn4linux@listserv.isdn4linux.de,
Al Viro <viro@zeniv.linux.org.uk>,
Holger Schurig <holgerschurig@googlemail.com>
Subject: Re: [PATCH 0/5] isdn: deprecate non-mISDN drivers
Date: Wed, 24 Apr 2019 23:28:47 +0200 [thread overview]
Message-ID: <1556140983@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <20190423151143.464992-1-arnd@arndb.de>
Arnd Bergmann wrote...
> If anyone is still using isdn4linux and CAPI with modern kernels, please
> speak up now.
Yeah, although I probably don't have much in defense. I am still using
it, mostly for isdnlog since I never got mISDN to work. I even wrote
the missing sysfs support for i4l some seven years but never had to guts
to submit it, mostly since it's not the best code and I never tested the
tty part of it. Some many ideas, so many plans, so little time.
But I do have to admit the great times of ISDN are in the past and will
not come back.
Christoph, also happens to be maintainer for the i4l userland in Debian
prev parent reply other threads:[~2019-04-24 21:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 15:11 [PATCH 0/5] isdn: deprecate non-mISDN drivers Arnd Bergmann
2019-04-23 15:11 ` [PATCH 1/5] isdn: gigaset: remove i4l support Arnd Bergmann
2019-04-23 15:11 ` [PATCH 2/5] isdn: remove hisax driver Arnd Bergmann
2019-04-23 15:11 ` [PATCH 3/5] isdn: remove isdn4linux Arnd Bergmann
2019-04-23 15:11 ` [PATCH 4/5] isdn: hdlc: move into mISDN Arnd Bergmann
2019-04-23 15:11 ` [PATCH 5/5] isdn: move capi drivers to staging Arnd Bergmann
2019-04-23 15:11 ` [PATCH 0/5] isdn: deprecate non-mISDN drivers Arnd Bergmann
2019-04-23 15:11 ` [PATCH 1/5] isdn: gigaset: remove i4l support Arnd Bergmann
2019-04-24 8:53 ` Paul Bolle
2019-04-24 12:33 ` Arnd Bergmann
2019-04-23 15:11 ` [PATCH 2/5] isdn: remove hisax driver Arnd Bergmann
2019-04-23 15:11 ` [PATCH 3/5] isdn: remove isdn4linux Arnd Bergmann
2019-04-23 15:11 ` [PATCH 4/5] isdn: hdlc: move into mISDN Arnd Bergmann
2019-04-23 15:11 ` [PATCH 5/5] isdn: move capi drivers to staging Arnd Bergmann
2019-04-24 9:24 ` Thomas Jarosch
2019-04-24 12:29 ` Arnd Bergmann
2019-04-24 13:06 ` Thomas Jarosch
2019-04-25 11:24 ` Arnd Bergmann
2019-04-29 9:58 ` Thomas Jarosch
2019-04-29 11:57 ` Arnd Bergmann
2019-04-24 2:37 ` [PATCH 0/5] isdn: deprecate non-mISDN drivers David Miller
2019-04-24 8:42 ` Arnd Bergmann
2019-04-24 10:24 ` Marcel Holtmann
2019-04-24 12:59 ` Arnd Bergmann
2019-04-24 14:30 ` Marcel Holtmann
2019-04-25 11:08 ` Arnd Bergmann
2019-04-25 11:21 ` Marcel Holtmann
2019-04-25 17:23 ` Paul Bolle
2019-04-24 7:56 ` Simon Horman
2019-04-24 8:14 ` Arnd Bergmann
2019-04-24 9:15 ` Simon Horman
2019-04-24 8:47 ` Paul Bolle
2019-04-24 11:48 ` Arnd Bergmann
2019-04-24 21:28 ` Christoph Biedl [this message]
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=1556140983@msgid.manchmal.in-ulm.de \
--to=isdn4linux.agzq@manchmal.in-ulm.de \
--cc=arnd@arndb.de \
--cc=gigaset307x-common@lists.sourceforge.net \
--cc=holgerschurig@googlemail.com \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=tilman@imap.cc \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).