From: Michael Krufky <mkrufky@m1k.net>
To: Linux and Kernel Video <video4linux-list@redhat.com>
Cc: Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bttv synchronizing patch
Date: Sat, 11 Jun 2005 02:45:22 -0400 [thread overview]
Message-ID: <42AA8882.40109@m1k.net> (raw)
In-Reply-To: <20050610175438.1553349d.akpm@osdl.org>
Andrew Morton wrote:
>Mauro Carvalho Chehab <mchehab@brturbo.com.br> wrote:
>
>
>> It is asked that *every* patch to V4L stuff to be first submitted to
>> video4linux-list@redhat.com.
>>
>>
>In that case you might want to double-check the patches which I have queued
>for post-2.6.12:
>
>fix-for-cx88-cardsc-for-dvico-fusionhdtv-3-gold-q.patch
>bttv-support-for-adlink-rtv24-capture-card.patch
>bttv-support-for-adlink-rtv24-capture-card-tidy.patch
>bttv-support-for-adlink-rtv24-capture-card-more-tidy.patch
>v4l-saa7134-ntsc-vbi-fix.patch
>v4l-pal-m-chroma-subcarrier-frequency-fix.patch
>video-for-linux-docummentation.patch
>v4l-add-support-for-pixelview-ultra-pro.patch
>dvico-fusionhdtv3-gold-t-documentation-fix.patch
>v4l-support-tuner-thomson-ddt-7611-atsc-ntsc.patch
>
>
The following three patches are from me:
fix-for-cx88-cardsc-for-dvico-fusionhdtv-3-gold-q.patch
dvico-fusionhdtv3-gold-t-documentation-fix.patch
v4l-support-tuner-thomson-ddt-7611-atsc-ntsc.patch
...and they depend on the following two patches submitted by Mauro:
video-for-linux-docummentation.patch
v4l-add-support-for-pixelview-ultra-pro.patch
...When these patches are applied in the order listed in Andrew's email, the result is the same as what I currently have in v4l cvs.
--
Michael Krufky
prev parent reply other threads:[~2005-06-11 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 17:31 [PATCH] bttv synchronizing patch Mauro Carvalho Chehab
[not found] ` <20050610175438.1553349d.akpm@osdl.org>
2005-06-11 6:45 ` Michael Krufky [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=42AA8882.40109@m1k.net \
--to=mkrufky@m1k.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
--cc=video4linux-list@redhat.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