linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: CIJOML <cijoml@volny.cz>, Adrian Bunk <bunk@stusta.de>,
	video4linux-list@redhat.com, linux-kernel@vger.kernel.org,
	linux-dvb-maintainer@linuxtv.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB updates
Date: Tue, 17 Apr 2007 00:42:23 -0300	[thread overview]
Message-ID: <1176781343.1459.44.camel@localhost> (raw)
In-Reply-To: <4623A391.9060604@linuxtv.org>

> > I have tested these patches with 2.6.20-mh1 + v4l-dvb-b5be3479f070 patchset.
> > I also tried 2.6.21-rc6 + v4l-dvb-b5be3479f070 patchset and this combination 
> > also works without OOPS.
> >   
> Yes, that shows that the changesets prevent the oops, but it says
> nothing about vanilla 2.6.20.y
> > Winfast dongles are both dvb-usb based (DiBcom 3000M-C and DiBcom DiB7000P), 
> > but pluto2 is cardbus (pci) based.
> >   
> just as I figured.  The pluto2 test results are great to hear, though --
> thank you.
> > I think we can include these patches into 2.6.21 and if we receive any 
> > problem, we still have 2.6.21.Z for fixing, don't we?
> 
> The stable kernel series is not there for that purpose.  It is not there
> to encourage a rush of patches into a final kernel release, only to
> cause potential problems, with the 2.6.x.y series as a fallback for
> fixes.  We should avoid the need for such last-minute fixes wherever
> possible.
For sure we should do the best to avoid regressions. But, IMO, a driver
for a hotpluggable device (USB) that can't support device hot plug is a
serious issue. 

If nobody have an issue pointing regressions on this, we should really
apply the fix for 2.6.21.

-- 
Cheers,
Mauro


  parent reply	other threads:[~2007-04-17  3:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 15:31 [GIT PATCHES] V4L/DVB updates Mauro Carvalho Chehab
2007-04-16  0:33 ` [v4l-dvb-maintainer] " Michael Krufky
2007-04-16  5:22   ` Manu Abraham
2007-04-16  8:17     ` Markus Rechberger
2007-04-16 10:00       ` Mauro Carvalho Chehab
2007-04-16 14:15   ` Adrian Bunk
2007-04-16 14:52     ` CIJOML
2007-04-16 15:00     ` CIJOML
2007-04-16 15:34     ` Michael Krufky
2007-04-16 16:16       ` Markus Rechberger
2007-04-27 21:34         ` Trent Piepho
2007-04-27 22:43           ` Markus Rechberger
2007-04-28  6:33             ` Trent Piepho
2007-04-28  9:47               ` Markus Rechberger
2007-04-16 16:18       ` CIJOML
2007-04-16 16:25         ` Michael Krufky
2007-04-16 22:15           ` hermann pitton
2007-04-17  3:42           ` Mauro Carvalho Chehab [this message]
2007-04-16 15:50 ` Dmitry Torokhov
2007-04-16 21:49   ` [v4l-dvb-maintainer] " Trent Piepho

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=1176781343.1459.44.camel@localhost \
    --to=mchehab@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=cijoml@volny.cz \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@linuxtv.org \
    --cc=torvalds@linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).