From: Hans Petter Selasky <hselasky@c2i.net>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Antti Palosaari <crope@iki.fi>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Juergen Lock <nox@jelal.kn-bremen.de>
Subject: Re: [PATCH, RFC] Fix DVB ioctls failing if frontend open/closed too fast
Date: Tue, 28 Aug 2012 22:56:41 +0200 [thread overview]
Message-ID: <201208282256.41157.hselasky@c2i.net> (raw)
In-Reply-To: <CAGoCfiyBZNkFkvhCqsbwxVaANZcp+1df-0eAmzrpzfavD6A+dQ@mail.gmail.com>
On Sunday 12 August 2012 05:06:49 Devin Heitmueller wrote:
> On Sat, Aug 11, 2012 at 10:15 PM, Mauro Carvalho Chehab
>
> <mchehab@redhat.com> wrote:
> > Devin/Antti,
> >
> > As Juergen mentioned your help on this patch, do you mind helping
> > reviewing and testing it?
>
> I guided Juergen through the creation of the patch via #linuxtv a
> couple of weeks ago. While I'm generally confident that it should
> work (and it does address his basic issue), I hadn't had the time to
> stare at the code long enough to see what other side effects it might
> produce.
>
> I'm tied up in other projects right now and am not confident I will
> have cycles to look at this closer. Antti, if you want to give it
> some cycles, this would be a good fix to get upstream (and you've
> already been looking at dvb_frontend.c for quite a while, so I believe
> you would be able to spot a problem if one exists).
>
> Devin
Hi,
What is the status of this PATCH? Submitted or under testing ??
--HPS
next prev parent reply other threads:[~2012-08-28 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 22:22 [PATCH, RFC] Fix DVB ioctls failing if frontend open/closed too fast Juergen Lock
2012-08-12 2:15 ` Fwd: " Mauro Carvalho Chehab
2012-08-12 3:06 ` Devin Heitmueller
2012-08-28 20:56 ` Hans Petter Selasky [this message]
2012-09-01 15:51 ` Fwd: " poma
2012-09-01 16:13 ` Antti Palosaari
2012-09-01 16:26 ` Devin Heitmueller
2012-09-01 16:38 ` Antti Palosaari
2012-09-26 20:11 ` [PATCH, RFC, updated] " Juergen Lock
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=201208282256.41157.hselasky@c2i.net \
--to=hselasky@c2i.net \
--cc=crope@iki.fi \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=nox@jelal.kn-bremen.de \
/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;
as well as URLs for NNTP newsgroup(s).