mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Linux and Kernel Video <video4linux-list@redhat.com>
Cc: v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] Re: [PATCH] V4L: struct video_device corruption
Date: Tue, 25 Jul 2006 14:59:33 -0300	[thread overview]
Message-ID: <1153850373.10875.18.camel@praia> (raw)
In-Reply-To: <Pine.LNX.4.58.0607241428070.8650@shell2.speakeasy.net>

Em Seg, 2006-07-24 às 15:06 -0700, Trent Piepho escreveu:
> On Mon, 24 Jul 2006, Mauro Carvalho Chehab wrote:
> > Em Dom, 2006-07-23 s 19:16 -0700, Trent Piepho escreveu:
> > > Second, the fix for class_device_create_file() doesn't roll-back properly
> > > on failure.  I already posted a patch which does this correctly.  Attached
> > > is the patch against the current Hg, go ahead and import it.
> > On your hg, there are 4 patches to be applied:
> >
> > 1) Fix bug where struct video_device was not defined consistently
> > This one seems to conflict with some previous changes I did. Please
> > remove it from your tree (you need to re-clone it - you may use hg-menu
> > to help on this stuff);
> 
> My Hg tree was outdated by your patches.  If you look at the time, I made
> that fix on Jul 20th, then your comprehensive patch on Jul 23rd
> incorporated that part of the fix.
The point is that your commit ask arrived after I've applied my patches.
> 
> > 3) Handle class_device_create_file in V4L2 drivers
> > The patch didn't applied well at current tree.
> 
> I know, that's why I attached a version to my email that would.  I have now
> re-done my tree to take into account the current code.
Applied. I'm submitting the current stuff to both mainstream and -mm
series.

Cheers, 
Mauro.


  reply	other threads:[~2006-07-25 18:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  4:43 oops in bttv Chuck Ebbert
2006-07-13  5:05 ` Greg KH
2006-07-13  5:24   ` Randy.Dunlap
2006-07-13  5:44     ` Andrew Morton
2006-07-15 23:08       ` [PATCH] V4L: struct video_device corruption Robert Fitzsimons
2006-07-16  1:31         ` Mauro Carvalho Chehab
2006-07-18  0:25           ` [v4l-dvb-maintainer] " Trent Piepho
2006-07-19 11:54             ` Mauro Carvalho Chehab
2006-07-19 15:36               ` Michael Krufky
2006-07-20 21:57               ` Trent Piepho
2006-07-21 12:26                 ` Mauro Carvalho Chehab
2006-07-21 20:06                   ` Trent Piepho
2006-07-21 20:30                     ` Mauro Carvalho Chehab
2006-07-21 22:55                       ` Trent Piepho
2006-07-23  9:35                         ` Mauro Carvalho Chehab
2006-07-24  2:16                           ` Trent Piepho
2006-07-24 12:34                             ` Mauro Carvalho Chehab
2006-07-24 22:06                               ` Trent Piepho
2006-07-25 17:59                                 ` Mauro Carvalho Chehab [this message]
2006-07-25  3:08           ` Andrew Morton
2006-07-25  7:57             ` [v4l-dvb-maintainer] " Manu Abraham
2006-07-25  8:42             ` Trent Piepho
2006-07-25  9:06               ` Andrew Morton
2006-07-25 12:28                 ` Mauro Carvalho Chehab

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=1153850373.10875.18.camel@praia \
    --to=mchehab@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v4l-dvb-maintainer@linuxtv.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