From: Ricardo Cerqueira <v4l@cerqueira.org>
To: linux-dvb-maintainer@linuxtv.org
Cc: video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB fixes
Date: Wed, 13 Feb 2008 20:36:44 +0000 [thread overview]
Message-ID: <1202935004.17260.54.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0802131025440.6264@shell2.speakeasy.net>
On Wed, 2008-02-13 at 10:45 -0800, Trent Piepho wrote:
> On Wed, 13 Feb 2008, Mauro Carvalho Chehab wrote:
> > On Tue, 12 Feb 2008 21:21:43 -0800 (PST)
> > Trent Piepho <xyzzy@speakeasy.org> wrote:
> >
> > The version with problems is the one dated by Jan, 16:
> > http://linuxtv.org/pipermail/v4l-dvb-maintainer/2008-January/006119.html
> >
> > As Ricardo stated on Feb, 5, he fixed the lock issues, that were present on
> > your first revision:
> >
> > http://linuxtv.org/pipermail/v4l-dvb-maintainer/2008-February/006292.html
>
> I don't see what you are saying in that message. Ricardo agreed it had a
> race condition and said he would, at some future point, redo it, but I
> never saw a new patch.
You missed it, then:
http://linuxtv.org/pipermail/v4l-dvb-maintainer/2008-February/006293.html
was sent in 25 minutes after the message Mauro mentioned.
> Nobody points to any issues, ever, when this happens. Look at how broken
> the v4l2 only bttv driver was. You still can't unload and load cx88-dvb
> since Markus's patch for hotplug, no one's fixed that regression. Now
> there's yet another race in the cx88 subdriver code. Maybe the original
> author who added that code should feel some motiviation to fix the
> regressions it caused....
Read the code that was actually committed: here's a helpful link:
http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=41a93616082af630e7242cba766a161d7847560b
>
> I don't have the time or the desire to be the janitor who cleans up after
> sloppy coders' bugs.
You properly raised a red flag, and got a fix in return.
Don't expect fixes to be accompanied by a "are you happy now?"
follow-up; if you took the time to check the first commit, take the time
to read the rest.
Now... it looks as if you simply missed the second patch; it happens.
But next time you feel like sending this kind of message(s) to 3
separate lists, at least check your mail history (or read the code
you're commenting).
--
RC
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-02-13 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 21:02 [GIT PATCHES] V4L/DVB fixes Mauro Carvalho Chehab
2008-02-13 5:21 ` [v4l-dvb-maintainer] " Trent Piepho
2008-02-13 17:53 ` Mauro Carvalho Chehab
2008-02-13 18:45 ` Trent Piepho
2008-02-13 20:36 ` Ricardo Cerqueira [this message]
2008-02-13 21:53 ` Trent Piepho
2008-02-13 22:50 ` Ricardo Cerqueira
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=1202935004.17260.54.camel@localhost.localdomain \
--to=v4l@cerqueira.org \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.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