mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Markus Rechberger" <mrechberger@gmail.com>
To: "Manu Abraham" <abraham.manu@gmail.com>
Cc: "Michael Krufky" <mkrufky@linuxtv.org>,
	linux-dvb-maintainer@linuxtv.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Mauro Carvalho Chehab" <mchehab@infradead.org>
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB updates
Date: Mon, 16 Apr 2007 10:17:10 +0200	[thread overview]
Message-ID: <d9def9db0704160117te51f4daxc4e92407ed87fddf@mail.gmail.com> (raw)
In-Reply-To: <46230806.7060908@gmail.com>

On 4/16/07, Manu Abraham <abraham.manu@gmail.com> wrote:
> Michael Krufky wrote:
> > Mauro,
> >
> > I've been out of town for the past few days... I just got home and saw
> this:
> >
> >
> > Mauro Carvalho Chehab wrote:
> >>    - Fix 1/3 for bug 7819: fixed frontend hotplug issue
> >>    - Fix 2/3 for bug 7819: demux and dvr
> >>    - Fix 3/3 for bug 7819: fixed hotplugging for dvbnet
> > I don't think that this is 2.6.21 material.  These patches have not yet
> > received
> > enough testing to be sent to mainline.
> >
> > I have tested them, and they seem to work for my cxusb device, but we have
> > yet to hear test results from users of usb dvb devices that do not use the
> > dvb-usb framework.  (ttusb, flexcop-usb, cinergyT2, for example)
> >
> > The bug that these patches fix has been around throughout the entire
> kernel
> > history of the dvb subsystem.  The bug is not a regression -- it has
> > always been
> > there.  In my opinion, it is too late in 2.6.21 development to apply
> > this change.
> > Because these fixes are not obvious, I think we should let them get some
> > more testing, and have them queued for 2.6.22 .
>
>
> I am not arguing about the veracity of the patches, but how things are
> handled.
>
> Agreed to all the mentioned above. There is one more aspect. The
> mentioned patches, do not have any ACK/SOB from any DVB
> developer/maintainer for the same.
>
> Huge regressions are created this way. One more time the regression
> creator is caught.
>

The patch has been around on the dvb mailinglist ([PATCH][RFC] DVB
Hotplug Fix, 5. April 2007), Michael looked at it when I told him
about it again separatly (12. April 2007)
Between that there was enough time to respond on it or review it.

Mauro told me at the beginning if noone responds he'll go forward
somehow because it fixes hotplugging, and after 2 weeks I wouldn't
expect anyone commenting that thread anymore.

It would be better to look and respond to that patch first before
responding about that you don't like how it's handled, Mauro also
wrote in his announcement that people should look at the recent
mercurial tree and he'll revert it if something doesn't work by
accident before submitting it to his git tree... still noone
complained about the hotplugging patch in there.

Markus

  reply	other threads:[~2007-04-16  8:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 15:31 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 [this message]
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
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=d9def9db0704160117te51f4daxc4e92407ed87fddf@mail.gmail.com \
    --to=mrechberger@gmail.com \
    --cc=abraham.manu@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mkrufky@linuxtv.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome