public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH RESEND] Fix bug in au0828 VBI streaming
Date: Thu, 03 Feb 2011 22:03:48 -0200	[thread overview]
Message-ID: <4D4B4264.9080705@redhat.com> (raw)
In-Reply-To: <AANLkTikyiS5_pkP_ALu3ogDioF+uqdA2D4H00Vz8iQsX@mail.gmail.com>

Em 03-02-2011 21:38, Devin Heitmueller escreveu:
> On Wed, Feb 2, 2011 at 8:58 AM, Devin Heitmueller
> <dheitmueller@kernellabs.com> wrote:
>> On Sun, Jan 23, 2011 at 5:12 PM, Devin Heitmueller
>> <dheitmueller@kernellabs.com> wrote:
>>> Attached is a patch for a V4L2 spec violation with regards to the
>>> au0828 not working in streaming mode.
>>>
>>> This was just an oversight on my part when I did the original VBI
>>> support for this bridge, as libzvbi was silently falling back to using
>>> the read() interface.
>>
>> Mauro,
>>
>> Where are we at with this patch.  It's trivial and VBI is broken in
>> V4L2 streaming mode without it.
> 
> Mauro,
> 
> I see this has been committed for 2.6.39.  Given the trivial nature,
> can we get it in there for 2.6.38 as well?  It's a bugfix and the
> au0828 VBI support is new to 2.6.38.  If it doesn't go in, then the
> VBI support will be present but broken for a full release cycle.  This
> could definitely cause problems for existing applications that now
> detect the presence of VBI support, but then break when they try to
> use it.

It is already on my local fixes tree. I'll be sending upstream together
with the next set of fixes.

Cheers,
Mauro

      reply	other threads:[~2011-02-04  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 22:12 [PATCH] Fix bug in au0828 VBI streaming Devin Heitmueller
2011-02-02 13:58 ` [PATCH RESEND] " Devin Heitmueller
2011-02-03 23:38   ` Devin Heitmueller
2011-02-04  0:03     ` Mauro Carvalho Chehab [this message]

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=4D4B4264.9080705@redhat.com \
    --to=mchehab@redhat.com \
    --cc=dheitmueller@kernellabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox