From: isdn@linux-pingi.de
To: Paul Bolle <pebolle@tiscali.nl>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: Re: Linux 5.0-rc1
Date: Mon, 11 Feb 2019 01:01:02 +0100 [thread overview]
Message-ID: <02380226-636a-ced5-bcd4-950ff01583e4@linux-pingi.de> (raw)
In-Reply-To: <3578229a062d10331dd0b8cfabe4b59a10e4ad2a.camel@tiscali.nl>
Hi all,
Am 09.02.19 um 20:42 schrieb Paul Bolle:
> Linus Torvalds schreef op zo 06-01-2019 om 18:14 [-0800]:
>> Nothing particular stands out, although I do like
>> seeing how some ancient drivers are getting put out to pasture
>> (*cought*isdn*cough*).
>
> Just to let people know: the gigaset drivers will get my palliative care until
> a few weeks before September 1, 2019. Because at that date the Dutch consumer
> grade ISDN network (the "BRI" part of ISDN) will be shut down. So expect a
> patch to remove me from MAINTAINERS sometime during the v5.2 cycle.
>
> That leaves just Karsten Keil to look after all the ISDN drivers. Karsten's
> last activity was in 2016. See commit 1e1589ad8b5c ("mISDN: Support DR6
> indication in mISDNipac driver"). Which is also the last commit apparently
> resolving an issue noticed by an actual _user_ of one of the ISDN drivers.
>
> Perhaps Karsten could tell us whether there's any point in keeping the ISDN
> subsystem in the tree after September 1, 2019, and if so, in what form. I'm in
> no position to properly answer that question.
I still follow the kernel ISDN patches. I very glad that Paul, Kees,
David and others handle everything without the need to jump in. I still
have some ISDN equipment running behind VOIP lines.
I do not think that here are so much direct users of BRI ISDN left, I
known only very few, but here are at least some.
mISDN is still used in embedded routers to emulate the classic ISDN S0
bus to use ISDN equipment on Internet based lines and last designs for
this usage are not so long ago (less a year ago, I know from questions I
got).
But of course ISDN is in palliative care and finally removing it is
maybe not a bad idea now.
Best
Karsten
next prev parent reply other threads:[~2019-02-11 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 2:14 Linus Torvalds
2019-01-07 5:07 ` linux-next: stats (was: Linux 5.0-rc1) Stephen Rothwell
2019-01-07 19:26 ` Linux 5.0-rc1 (test results) Guenter Roeck
2019-01-07 23:21 ` Linus Torvalds
2019-01-08 9:51 ` Guo Ren
2019-01-08 15:40 ` Michal Hocko
2019-01-08 16:16 ` Guo Ren
2019-01-08 17:29 ` Michal Hocko
2019-02-09 19:42 ` Linux 5.0-rc1 Paul Bolle
2019-02-11 0:01 ` isdn [this message]
2019-01-10 5:10 unconditionedwitness
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=02380226-636a-ced5-bcd4-950ff01583e4@linux-pingi.de \
--to=isdn@linux-pingi.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®