From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Patch update notification: 37 patches updated
Date: Sun, 23 Dec 2012 12:57:15 -0200 [thread overview]
Message-ID: <20121223125715.782e17e0@redhat.com> (raw)
In-Reply-To: <50D70AFB.5070702@googlemail.com>
Em Sun, 23 Dec 2012 14:45:31 +0100
Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:
> Hi Mauro,
>
> Am 23.12.2012 01:08, schrieb Patchwork:
> > Hello,
> >
> > The following patches (submitted by you) have been updated in patchwork:
> >
> > * [3/6] em28xx: fix capture type setting in em28xx_urb_data_copy_vbi()
> > - http://patchwork.linuxtv.org/patch/15651/
> > was: New
> > now: Accepted
> >
> > * [8/9] em28xx: move the em2710/em2750/em28xx specific frame data processing code to a separate function
> > - http://patchwork.linuxtv.org/patch/15798/
> > was: New
> > now: Accepted
> >
> > * [4/6] em28xx: fix/improve frame field handling in em28xx_urb_data_copy_vbi()
> > - http://patchwork.linuxtv.org/patch/15652/
> > was: New
> > now: Accepted
>
> This patch has not been applied yet to the media-tree.
> Without this patch, frame data processing for non-interlaced devices is
> broken.
Not sure what happened there: I couldn't see this specific patch. Yet,
at least some of the changes there seem to be applied. My guess is that
somehow, this patch got merged with some other patch, or maybe the
conflicts solving when the vbi-merge patches got applied (partially)
fixed it.
In any case, you'll need to rebase it, as it doesn't apply anymore.
Cheers,
Mauro
next prev parent reply other threads:[~2012-12-23 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121223000802.14820.14465@www.linuxtv.org>
2012-12-23 13:45 ` Patch update notification: 37 patches updated Frank Schäfer
2012-12-23 14:57 ` Mauro Carvalho Chehab [this message]
2012-12-24 10:56 ` Frank Schäfer
2012-12-24 15:06 ` Mauro Carvalho Chehab
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=20121223125715.782e17e0@redhat.com \
--to=mchehab@redhat.com \
--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 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).