From: Michael Krufky <mkrufky@m1k.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc2-mm1
Date: Thu, 07 Jul 2005 08:46:32 -0400 [thread overview]
Message-ID: <42CD2428.4090406@m1k.net> (raw)
In-Reply-To: <20050707040037.04366e4e.akpm@osdl.org>
Andrew Morton wrote:
>- I seem to have quite a bit of material here which is appropriate to
> 2.6.13:
>
> - all the DVB patches
>
> - all the v4l patches
>
>- Anything which you think needs to go into 2.6.13, please let me know.
>
>
>dvb-frontend-add-driver-for-lgdt3302.patch
> dvb: frontend: add driver for LGDT3302
>
>v4l-cx88-update.patch
> v4l: cx88 update
>
>
This (v4l-cx88-update.patch) can go to 2.6.13 whenever you are ready.
>v4l-cx88-hue-offset-fix.patch
> v4l: cx88 hue offset fix
>
>
This (v4l-cx88-hue-offset-fix.patch) should be merged into 2.6.13
immediately -- It is a one-line fix that corrects a bug that causes
incorrect hue settings behavior in all cx88 chips. It is also in Chris
Wright's stable patch queue.
>v4l-add-dvb-support-for-dvico-fusionhdtv3-gold-q.patch
> v4l: add DVB support for DViCO FusionHDTV3 Gold-Q
>
>v4l-add-terratec-cinergy-1400-dvb-t.patch
> v4l: add TerraTec Cinergy 1400 DVB-T
>
>v4l-add-dvb-support-for-dvico-fusionhdtv3-gold-t.patch
> v4l: add DVB support for DViCO FusionHDTV3 Gold-T
>
>v4l-lgdt3302-read-status-fix.patch
> v4l: LGDT3302 read status fix
>
>
This (v4l-lgdt3302-read-status-fix.patch) is actually a dvb patch.
There are two v4l boards that use the lgdt3302 dvb frontend, and these
are the only known (supported) boards to use lgdt3302 at this time.
This patch should go to 2.6.13 whenever
(dvb-frontend-add-driver-for-lgdt3302.patch) does, as it corrects a
major bug.
Come to think of it, dvb-frontend-add-driver-for-lgdt3302.patch is
pretty much useless without the following patches:
v4l-add-dvb-support-for-dvico-fusionhdtv3-gold-q.patch
v4l-add-dvb-support-for-dvico-fusionhdtv3-gold-t.patch
v4l-lgdt3302-read-status-fix.patch
...so whenever the lgdt3302 stuff is going into 2.6.13, all four of these patches should go together.
Thank you!
--
Michael Krufky
next prev parent reply other threads:[~2005-07-07 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 11:00 2.6.13-rc2-mm1 Andrew Morton
2005-07-07 11:27 ` 2.6.13-rc2-mm1 Miklos Szeredi
2005-07-07 11:34 ` 2.6.13-rc2-mm1 Andrew Morton
2005-07-07 11:44 ` 2.6.13-rc2-mm1 Miklos Szeredi
2005-07-07 11:32 ` 2.6.13-rc2-mm1 Brice Goglin
2005-07-07 11:42 ` 2.6.13-rc2-mm1 Andrew Morton
2005-07-07 11:44 ` 2.6.13-rc2-mm1 Brice Goglin
2005-07-07 12:46 ` Michael Krufky [this message]
2005-07-07 14:19 ` 2.6.13-rc2-mm1 Robert Love
2005-07-07 16:14 ` 2.6.13-rc2-mm1 Roland Dreier
2005-07-09 2:07 ` 2.6.13-rc2-mm1: some speakup nitpicks Adrian Bunk
2005-07-09 3:02 ` Greg KH
2005-07-09 13:16 ` Alexey Dobriyan
2005-07-11 16:29 ` 2.6.13-rc2-mm1 - unknown symbol: is_broadcast_ether_addr Damir Perisa
-- strict thread matches above, loose matches on Subject: below --
2005-07-07 21:38 2.6.13-rc2-mm1 jan malstrom
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=42CD2428.4090406@m1k.net \
--to=mkrufky@m1k.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@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