From: Antti Palosaari <crope@iki.fi>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: em28xx DEADLOCK reported by lock debug
Date: Sun, 22 Dec 2013 16:34:43 +0200 [thread overview]
Message-ID: <52B6F883.8060103@iki.fi> (raw)
In-Reply-To: <52B6EE79.9070105@googlemail.com>
On 22.12.2013 15:51, Frank Schäfer wrote:
> Am 21.12.2013 20:55, schrieb Antti Palosaari:
>> On 21.12.2013 18:51, Frank Schäfer wrote:
>>> Hi Antti,
>>>
>>> thank you for reporting this issue.
>>>
>>> Am 18.12.2013 17:04, schrieb Antti Palosaari:
>>>> That same lock debug deadlock is still there (maybe ~4 times I report
>>>> it during 2 years). Is that possible to fix easily at all?
>>>
>>> Patches are always welcome. ;)
>>
>> haha, I cannot simply learn every driver I meet some problems...
> Hint:
>
> If you report a bug ~4 times in 2 years but never get a reply, it
> usually means
> a) nobody cares
> b) nobody has the resources (time, knowledge) to fix it.
>
> So you either have to live with this issue or to fix it yourself.
OK, as you request me to fix it, I will fix that by making DVB USB v2
driver for these em28xx devices I have added.
It should not be very much work as em28xx protocol is still relatively easy.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2013-12-22 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 16:04 em28xx DEADLOCK reported by lock debug Antti Palosaari
2013-12-21 16:51 ` Frank Schäfer
2013-12-21 19:55 ` Antti Palosaari
2013-12-22 13:51 ` Frank Schäfer
2013-12-22 14:34 ` Antti Palosaari [this message]
2013-12-22 18:02 ` Frank Schäfer
2013-12-22 18:14 ` Antti Palosaari
2013-12-22 18:51 ` Frank Schäfer
2013-12-22 14:53 ` Mauro Carvalho Chehab
2013-12-22 18:12 ` Frank Schäfer
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=52B6F883.8060103@iki.fi \
--to=crope@iki.fi \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-media@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.