From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Jiri Slaby <jirislaby@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Patrick Boettcher <pboettcher@kernellabs.com>
Subject: Re: [PATCH 1/1] DVB-USB: dib0700, fix oops with non-dib7000pc devices
Date: Thu, 24 Feb 2011 10:49:24 -0300 [thread overview]
Message-ID: <4D6661E4.6040505@infradead.org> (raw)
In-Reply-To: <4D665FFF.7050501@suse.cz>
Em 24-02-2011 10:41, Jiri Slaby escreveu:
> On 02/24/2011 01:53 PM, Mauro Carvalho Chehab wrote:
>> Em 24-02-2011 09:24, Jiri Slaby escreveu:
>>> Hmm, could anybody pick it up?
>>>
>>> On 02/05/2011 07:20 PM, Jiri Slaby wrote:
>>>> These devices use different internal structures (dib7000m) and
>>>> dib7000p pid ctrl accesses invalid members causing kernel to die.
>>>>
>>>> Introduce pid control functions for dib7000m which operate on the
>>>> correct structure.
>>
>> Patrick (DibCom drivers maintainer) has proposed an alternate patch for it [1]
>> that properly address the issues:
>>
>> http://git.linuxtv.org/pb/media_tree.git?a=commitdiff;h=80a5f1fdc6beb496347cbb297f9c1458c8cb9f50
>>
>> [1] http://www.spinics.net/lists/linux-media/msg27890.html
>>
>> Could you please test it?
>
> Yes, I will later.
>
> Is there any reason why this is not in Linus' and stable trees and
> mainly in linux/next already?
Yes. I'm waiting for confirmation that this patch fixes the reported issue.
Cheers,
Mauro
next prev parent reply other threads:[~2011-02-24 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 18:20 [PATCH 1/1] DVB-USB: dib0700, fix oops with non-dib7000pc devices Jiri Slaby
2011-02-24 12:24 ` Jiri Slaby
2011-02-24 12:53 ` Mauro Carvalho Chehab
2011-02-24 13:41 ` Jiri Slaby
2011-02-24 13:49 ` Mauro Carvalho Chehab [this message]
2011-02-25 6:57 ` Jiri Slaby
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=4D6661E4.6040505@infradead.org \
--to=mchehab@infradead.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pboettcher@kernellabs.com \
/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