From: Samuel Ortiz <samuel@sortiz.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
Network Development <netdev@vger.kernel.org>
Subject: Re: IrDA woes..
Date: Sat, 04 Jan 2014 02:23:31 +0100 [thread overview]
Message-ID: <1388798611.4326.11.camel@zurbaran> (raw)
In-Reply-To: <CA+55aFz_qDYP_P0PLUNv0wotoy=5PcS+7Qtt=U6EzvL4h4E69A@mail.gmail.com>
Hi Linus,
On Thu, 2014-01-02 at 11:11 -0800, Linus Torvalds wrote:
> The odd thing is that I *have* seen it work, a couple of times, so
> it's not like it *never* works (in which case I'd just think that the
> above simply isn't even supposed to work at all), but the "it actually
> worked" is a very rare occurrence. Most of the time opening the ircomm
> blocks. But sometimes it works after a few seconds. Very odd.
I'm pretty sure the stack was never designed nor tested for that kind of
usage, so I'm even surprised it ever worked for you.
> Samuel is listed as maintainer, but I'm getting the feeling he has
> long since moved on.
That's correct, and the MAINTAINERS file should be updated I guess.
The combination of my last IrDA enabled phone dying and the IrDA
association removing my access to the specs significantly lowered my
interest.
Cheers,
Samuel.
next prev parent reply other threads:[~2014-01-04 1:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 20:08 IrDA woes Linus Torvalds
2014-01-02 8:46 ` David Miller
2014-01-02 19:11 ` Linus Torvalds
2014-01-02 21:07 ` Linus Torvalds
2014-01-02 22:41 ` David Miller
2014-01-02 22:47 ` Linus Torvalds
2014-01-03 0:05 ` David Miller
2014-01-03 1:00 ` Linus Torvalds
2014-01-02 21:41 ` Marcel Holtmann
2014-01-02 21:49 ` Linus Torvalds
2014-01-02 22:13 ` Marcel Holtmann
2014-01-02 22:29 ` Linus Torvalds
2014-01-02 22:54 ` Linus Torvalds
2014-01-02 22:42 ` David Miller
2014-01-04 1:23 ` Samuel Ortiz [this message]
2014-01-04 8:15 ` Loganaden Velvindron
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=1388798611.4326.11.camel@zurbaran \
--to=samuel@sortiz.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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