mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trent Piepho <xyzzy@speakeasy.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-dvb-maintainer@linuxtv.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	video4linux-list@redhat.com, linux-kernel@vger.kernel.org,
	Ricardo Cerqueira <ricardo@cerqueira.org>
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB fixes
Date: Wed, 13 Feb 2008 10:45:06 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0802131025440.6264@shell2.speakeasy.net> (raw)
In-Reply-To: <20080213155352.06d966cd@gaivota>

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:
>
> > On Tue, 12 Feb 2008, Mauro Carvalho Chehab wrote:
> > >    - cx88-mpeg: Allow concurrent access to cx88-mpeg devices;
> >
> > So you decided to just commit this one with the race condition anyway?
>
> 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.

> I've pushed the reviewed version at the same day, for testing, at the

review-by == I saw your patch in my inbox and read the title

> development environment:
>
> http://linuxtv.org/pipermail/v4l-dvb-maintainer/2008-February/006326.html
>
> Nobody pointed any newer issues on the reviewed version, since then.

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....

The only complaints that are ever generated on commits to the development
enviroment are political, "so-and-so shouldn't be able to patch my
fiefdom."

> If you still see any issues, please send us a patch fixing it.

I don't have the time or the desire to be the janitor who cleans up after
sloppy coders' bugs.

  reply	other threads:[~2008-02-13 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 21:02 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 [this message]
2008-02-13 20:36       ` Ricardo Cerqueira
2008-02-13 21:53         ` Trent Piepho
2008-02-13 22:50           ` Ricardo Cerqueira
  -- strict thread matches above, loose matches on Subject: below --
2007-12-12  1:05 Mauro Carvalho Chehab
     [not found] ` <475F4422.6050000@linuxtv.org>
2007-12-12  2:33   ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2007-12-12  2:36     ` Mauro Carvalho Chehab
2007-12-12  3:10       ` Michael Krufky

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=Pine.LNX.4.58.0802131025440.6264@shell2.speakeasy.net \
    --to=xyzzy@speakeasy.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=ricardo@cerqueira.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

Powered by JetHome