linux-kernel - Re: [PATCH v2] media: ti-vpe: Use mem-to-mem ioctl helpers

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: <54CBAB4E.3040805@xs4all.nl>
Date:	Fri, 30 Jan 2015 17:03:26 +0100
From:	Hans Verkuil <hverkuil@...all.nl>
To:	"Lad, Prabhakar" <prabhakar.csengg@...il.com>,
	Hans Verkuil <hans.verkuil@...co.com>,
	Kamil Debski <k.debski@...sung.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	LMML <linux-media@...r.kernel.org>
Subject: Re: [PATCH v2] media: ti-vpe: Use mem-to-mem ioctl helpers

Hi Prabhakar,

I might have time on Monday, but that is almost certainly too late
for 3.20. It's a bit busy at the moment.

Sorry,

	Hans

On 01/30/2015 04:54 PM, Lad, Prabhakar wrote:
> Hello Hans/Kamil,
> 
> On Fri, Dec 19, 2014 at 1:52 PM, Lad, Prabhakar
> <prabhakar.csengg@...il.com> wrote:
>> 1: Simplify the vpe mem-to-mem driver by using the m2m ioctl
>>    and vb2 helpers.
>> 2: Align and arranged the v4l2_ioctl_ops.
>> 3: Fixes a typo.
>> 4: Use of_match_ptr() instead of explicitly defining the macro
>>    to NULL in case CONFIG_OF is not defined.
>>
> Can you please review and queue this patch for v3.20 ?
> 
> Cheers,
> --Prabhakar Lad
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
--
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/