From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: Boris BREZILLON <boris.brezillon@free-electrons.com>
Cc: Rob Clark <robdclark@gmail.com>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] drm: rework flip-work framework
Date: Tue, 12 Aug 2014 13:14:07 +0200 [thread overview]
Message-ID: <20140812131407.069635e8@bbrezillon> (raw)
In-Reply-To: <1405173968-23869-1-git-send-email-boris.brezillon@free-electrons.com>
Hi,
On Sat, 12 Jul 2014 16:06:06 +0200
Boris BREZILLON <boris.brezillon@free-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 ?
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-12 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 14:06 Boris BREZILLON
2014-07-12 14:06 ` [PATCH v3 1/2] drm: rework flip-work helpers to avoid calling func when the FIFO is full Boris BREZILLON
2014-07-12 14:06 ` [PATCH v3 2/2] drm: flip-work: change drm_flip_work_init prototype Boris BREZILLON
2014-08-12 11:14 ` Boris BREZILLON [this message]
2014-08-12 11:20 ` [PATCH v3 0/2] drm: rework flip-work framework Rob Clark
2014-08-12 11:30 ` Boris BREZILLON
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=20140812131407.069635e8@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.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
all inboxes | Powered by JetHome®