From: Gerd Hoffmann <kraxel@redhat.com>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>,
dri-devel@lists.freedesktop.org
Cc: airlied@redhat.com, daniel.vetter@intel.com
Subject: Re: [PATCH] drm: qxl: Delay entering atomic context during cursor update
Date: Tue, 23 May 2017 09:19:33 +0200 [thread overview]
Message-ID: <1495523973.30747.0.camel@redhat.com> (raw)
In-Reply-To: <20170519175819.15682-1-krisman@collabora.co.uk>
On Fri, 2017-05-19 at 14:58 -0300, Gabriel Krisman Bertazi wrote:
> Hi Dave,
>
> This is -rc material. Once Gerd and others are happy with it, we
> should
> queue for 4.12.
>
Applied to drm-misc-fixes.
thanks,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-05-23 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 17:58 [PATCH] drm: qxl: Delay entering atomic context during cursor update Gabriel Krisman Bertazi
2017-05-23 7:19 ` Gerd Hoffmann [this message]
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=1495523973.30747.0.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=krisman@collabora.co.uk \
/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