lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <abe312a35d10b0478d4ea1f51da14860f017b921.camel@tiscali.nl> Date: Thu, 25 Apr 2019 19:23:51 +0200 From: Paul Bolle <pebolle@...cali.nl> To: Arnd Bergmann <arnd@...db.de>, Marcel Holtmann <marcel@...tmann.org> Cc: Greg KH <gregkh@...uxfoundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, "David S. Miller" <davem@...emloft.net>, Karsten Keil <isdn@...ux-pingi.de>, Networking <netdev@...r.kernel.org>, isdn4linux@...tserv.isdn4linux.de, Holger Schurig <holgerschurig@...glemail.com>, Tilman Schmidt <tilman@...p.cc>, Al Viro <viro@...iv.linux.org.uk>, gigaset307x-common@...ts.sourceforge.net, Johan Hedberg <johan.hedberg@...il.com>, Bluez mailing list <linux-bluetooth@...r.kernel.org> Subject: Re: [PATCH 0/5] isdn: deprecate non-mISDN drivers Arnd Bergmann schreef op do 25-04-2019 om 13:08 [+0200]: > The gigaset driver is similar here, you can use it for any kind of wireless ISDN > communication, Nit: the wireless part is strictly DECT (for the M101 and M105 hardware). > but apparently there is little use for that without a physical > ISDN connection. Probably. The main point is that once my ISDN line is canceled it would be nice to know whether someone still cares about these drivers. (Do note that for day to day data traffic I definitely do not really on ISDN. I'm not _that_ crazy.) Your suggestion to exile them into drivers/staging is about the only policy we have for finding that out. Thanks, Paul Bolle
Powered by blists - more mailing lists