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 22:50:18 +0000 [thread overview]
Message-ID: <1202943018.4064.37.camel@frolic> (raw)
In-Reply-To: <Pine.LNX.4.58.0802131349400.6264@shell2.speakeasy.net>
On Wed, 2008-02-13 at 13:53 -0800, Trent Piepho wrote:
> On Wed, 13 Feb 2008, Ricardo Cerqueira wrote:
> > 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:
> > > >
> > 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 did. Looks like there is a race on access to core->active_ref.
You're right, I missed that. A patch has already been sent to the
V4L/DVB list.
> You could also CC the relevant parties. Unless you're hoping they won't
> notice something.
Sorry, but no. I actively try *not* to send duplicate e-mails to people
unless they specifically request it.
--
RC
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
prev parent reply other threads:[~2008-02-13 22:50 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
2008-02-13 21:53 ` Trent Piepho
2008-02-13 22:50 ` Ricardo Cerqueira [this message]
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=1202943018.4064.37.camel@frolic \
--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