From: "Keith Packard" <keithp@keithp.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5]: drm: Add drm mode object leases
Date: Mon, 16 Oct 2017 10:52:11 -0700 [thread overview]
Message-ID: <874lqzx9o4.fsf@keithp.com> (raw)
In-Reply-To: <20171016091316.zxw2ktugfblikp3m@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
Daniel Vetter <daniel@ffwll.ch> writes:
> A bit lacking time to do an in-depth review, but all my major concerns
> seem to be addressed. On the series.
Thanks much.
I sent out a note over the weekend about how we can make the Vulkan API
work without the permissions change in the kernel. We need to provide
access to a DRM master and can choose to either use the X server's or
pass a master FD in explicitly.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-10-16 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 1:56 [PATCH 0/5]: drm: Add drm mode object leases Keith Packard
2017-10-13 1:56 ` [PATCH 1/5] drm/plane: drop num_overlay_planes (v2) Keith Packard
2017-10-16 19:23 ` Sean Paul
2017-10-13 1:56 ` [PATCH 2/5] drm: Add new LEASE debug level Keith Packard
2017-10-16 19:24 ` Sean Paul
2017-10-13 1:56 ` [PATCH 3/5] drm: Add drm_object lease infrastructure [v4] Keith Packard
2017-10-16 19:44 ` Sean Paul
2017-10-16 20:42 ` Keith Packard
2017-10-16 21:05 ` Sean Paul
2017-10-13 1:56 ` [PATCH 4/5] drm: Check mode object lease status in all master ioctl paths [v3] Keith Packard
2017-10-16 20:34 ` Sean Paul
2017-10-13 1:56 ` [PATCH 5/5] drm: Add four ioctls for managing drm mode object leases [v6] Keith Packard
2017-10-16 21:03 ` Sean Paul
2017-10-16 21:31 ` Keith Packard
2017-10-16 9:13 ` [PATCH 0/5]: drm: Add drm mode object leases Daniel Vetter
2017-10-16 17:52 ` Keith Packard [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=874lqzx9o4.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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