linux-kernel - Re: [GIT PATCHES FOR 2.6.36] gspca for

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: <4C25FDA0.2020800@redhat.com>
Date:	Sat, 26 Jun 2010 10:16:16 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Jean-Francois Moine <moinejf@...e.fr>
CC:	linux-media@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [GIT PATCHES FOR 2.6.36] gspca for_2.6.36

Em 22-06-2010 05:42, Jean-Francois Moine escreveu:
> On Mon, 21 Jun 2010 22:23:21 -0300

>> I'm applying the remaining patches. If you think that this patch is
>> correct, please re-send it to both LMML and LKML, c/c the authors of
>> the slab.h removal, in order to get their acks, or, otherwise, please
>> re-submit it for 2.6.37 window.
> 
> Hi Mauro,
> 
> The slab.h dependency was changed in the kernel 2.6.34 and its
> inclusion in some gspca source files was needed in case of the usage of
> kmalloc/kfree only.
> 
> After removing the JPEG header allocation, most gspca subdrivers do not
> use alloc/free anymore, so, there is no need to include slab.h anymore.
> 
> On the other side, this patch is easily checked because, if wrong, it
> raises compilation errors on any architecture.
> 
> Then, both patches (removal of JPEG alloc/free and slab.h inclusion)
> should go to 2.6.36.

OK, makes sense. I'll apply the patch at staging/gspca.

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/