From: Adrian Bunk <bunk@stusta.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.30-pre1
Date: Mon, 25 Sep 2006 03:20:37 +0200 [thread overview]
Message-ID: <20060925012037.GD4547@stusta.de> (raw)
In-Reply-To: <20060924101255.GA4813@ucw.cz>
On Sun, Sep 24, 2006 at 10:12:55AM +0000, Pavel Machek wrote:
> Hi!
>
> > > > Andrew Burri:
> > > > V4L/DVB: Add support for Kworld ATSC110
> > > >
> > > > Curt Meyers:
> > > > V4L/DVB: KWorld ATSC110: implement set_pll_input
> > > > V4L/DVB: Kworld ATSC110: enable composite and svideo inputs
> > > > V4L/DVB: Kworld ATSC110: initialize the tuner for analog mode on module load
> > > >
> > > > Giampiero Giancipoli:
> > > > V4L/DVB: Added support for the LifeView FlyDVB-T LR301 card
> > > >
> > > > Hartmut Hackmann:
> > > > V4L/DVB: Added support for the ADS Instant TV DUO Cardbus PTV331
> > > > V4L/DVB: Added PCI IDs of 2 LifeView Cards
> > > > V4L/DVB: Corrected CVBS input for the AVERMEDIA 777 DVB-T
> > > > V4L/DVB: Added support for the new Lifeview hybrid cardbus modules
> > > > V4L/DVB: TDA10046 Driver update
> > > > V4L/DVB: TDA8290 update
> > > >
> > > > Peter Hartshorn:
> > > > V4L/DVB: Added support for the Tevion DVB-T 220RF card
> > >
> > > Hm, all of these patches seems like these are new features being
> > > backported to the 2.6.16.y kernel, which is not really allowed under the
> > > current -stable rules.
> > >
> > > Or are these patches just bugfixes that fix with the current -stable
> > > rules?
> >
> > They add support for additional hardware to the saa7134 driver.
> >
> > If you look at the actual diff there's not much that could cause any
> > regression since nearly all of these change don't change anything for
> > the already supported cards.
> >
> > As long as there's not a serious risk of regressions, such additions are
> > welcome in 2.6.16.
>
> I believe you should not do that. Maybe risk of regression is small,
> but risk of adding non-working driver is not,
If it didn't work before and doesn't work after, nothing changed.
> and goal of -stable is
> to be stable, not to have feature-of-the-day.
No disagreement.
> Pavel
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-09-25 1:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 22:23 Linux 2.6.16.30-pre1 Adrian Bunk
2006-09-22 22:38 ` Greg KH
2006-09-22 22:47 ` Adrian Bunk
2006-09-22 23:09 ` Greg KH
2006-09-23 4:56 ` Willy Tarreau
2006-09-23 23:21 ` Adrian Bunk
2006-09-23 23:53 ` Willy Tarreau
2006-09-24 7:46 ` Sergey Vlasov
2006-09-24 18:16 ` Adrian Bunk
2006-09-24 19:46 ` Stefan Richter
2006-09-24 19:44 ` Willy Tarreau
2006-09-24 20:02 ` Willy Tarreau
2006-09-25 1:01 ` Adrian Bunk
2006-09-24 10:17 ` Pavel Machek
2006-09-25 1:23 ` Adrian Bunk
2006-09-25 8:15 ` Pavel Machek
2006-09-27 5:14 ` Greg KH
2006-09-23 20:49 ` Jean Delvare
2006-09-23 20:57 ` Lee Revell
2006-09-23 21:20 ` Jean Delvare
2006-09-23 22:47 ` Adrian Bunk
2006-09-23 22:33 ` Adrian Bunk
2006-09-23 22:47 ` Lee Revell
2006-09-23 22:58 ` Adrian Bunk
2006-09-23 22:12 ` Adrian Bunk
2006-09-24 10:12 ` Pavel Machek
2006-09-25 1:20 ` Adrian Bunk [this message]
2006-09-24 20:25 ` Grant Coady
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=20060925012037.GD4547@stusta.de \
--to=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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