linux-kernel - Re: [PATCH v3 0/2] drm: rework flip-work framework

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Aug 2014 07:20:09 -0400
From:	Rob Clark <robdclark@...il.com>
To:	Boris BREZILLON <boris.brezillon@...e-electrons.com>
Cc:	David Airlie <airlied@...ux.ie>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] drm: rework flip-work framework

On Tue, Aug 12, 2014 at 7:14 AM, Boris BREZILLON
<boris.brezillon@...e-electrons.com> wrote:
> Hi,
>
> On Sat, 12 Jul 2014 16:06:06 +0200
> Boris BREZILLON <boris.brezillon@...e-electrons.com> wrote:
>
>> Hello,
>>
>> This patch series reworks the flip-work framework to make it safe when
>> calling drm_flip_work_queue from atomic contexts.
>>
>> The 2nd patch of this series is optional, as it only reworks
>> drm_flip_work_init prototype to remove unneeded size argument and
>> return code (this function cannot fail anymore).
>
>
> Atmel HLCDC driver now depends on this series and I'd like to get as
> much thing as possible for HLCDC support in 3.18 (if the driver can't
> make it for 3.18, at least the dependencies could).
>
> David, Rob (and other DRM/KMS developers) do you have any concern you
> would like addressed in this patch series ?

it already has my r-b :-)

BR,
-R

> Best Regards,
>
> Boris
>
>
> --
> Boris Brezillon, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
--
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/