From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 198657] New: irda scheduled for removal
Date: Sat, 3 Feb 2018 12:38:43 -0800 [thread overview]
Message-ID: <20180203123843.3cfaf05d@xeon-e3> (raw)
Begin forwarded message:
Date: Sat, 03 Feb 2018 20:24:46 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 198657] New: irda scheduled for removal
https://bugzilla.kernel.org/show_bug.cgi?id=198657
Bug ID: 198657
Summary: irda scheduled for removal
Product: Networking
Version: 2.5
Kernel Version: 4.14
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: kernel@cschramm.eu
Regression: No
Hi,
I just wanted to do my regular download from my dive computer, plugged in my
USB IrDA dongle, ran irattach, hit the download button in surbsurface and got
an error message. It turns out that my system does not support AF_IRDA anymore
after upgrading to Linux 4.14 as the Linux developers scheduled the subsystem
for removal and the Debian maintainers decided to disable it already due to
that.
It seems like I am not the only one surprised by the statement that nobody
seems to use it and it's broken: https://lkml.org/lkml/2017/8/29/773
libdivecomputer does use it [1] and I do use it via libdivecomputer. It works
fine. While I agree that IrDA isn't the best decision today, my dive computer
is neither exotic nor very old.
[1] https://github.com/libdivecomputer/libdivecomputer/blob/master/src/irda.c
I ask you to reconsider the decision to drop the irda subsystem.
Regards
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-02-03 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180203123843.3cfaf05d@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@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