lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1153850373.10875.18.camel@praia>
Date:	Tue, 25 Jul 2006 14:59:33 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Linux and Kernel Video <video4linux-list@...hat.com>
Cc:	v4l-dvb maintainer list <v4l-dvb-maintainer@...uxtv.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [v4l-dvb-maintainer] Re: [PATCH] V4L: struct video_device
	corruption

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ