From: Dave Airlie <airlied@gmail.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/7] some cleanups and uapi clarification for leases
Date: Fri, 5 Apr 2019 12:40:14 +1000 [thread overview]
Message-ID: <CAPM=9tz90rbbYCZS5377cEwM7MPyMjnW6CWWqdoAmai8fa+3ZQ@mail.gmail.com> (raw)
In-Reply-To: <20190314095839.38fb95d1@collabora.com>
On Thu, 14 Mar 2019 at 18:58, Boris Brezillon
<boris.brezillon@collabora.com> wrote:
>
> On Thu, 28 Feb 2019 15:49:03 +0100
> Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> > Hi all,
> >
> > Nothing too major, only things I did find in all my igt test extending for
> > drm lease is some corner cases around implicit planes and atomic target
> > crtcs. Review and comments very much appreciated.
> >
> > Cheers, Daniel
> >
> > Test-with: 20190228141918.26043-1-daniel.vetter@ffwll.ch
> >
> > Daniel Vetter (7):
> > drm/leases: Drop object_id validation for negative ids
> > drm/lease: Drop recursive leads checks
> > drm/leases: Don't init to 0 in drm_master_create
> > drm/lease: Check for lessor outside of locks
> > drm/lease: Make sure implicit planes are leased
> > drm/atomic: Wire file_priv through for property changes
> > drm/atomic: -EACCESS for lease-denied crtc lookup
>
> I had a look at patches 5-7 and they seem to do the right thing, but my
> knowledge on DRM leases is quite limited, and given all the corner
> cases of legacy CRTC/plane updates, I'm not comfortable adding my R-b
> on these.
For the series:
Reviewed-by: Dave Airlie <airlied@redhat.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-05 2:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 14:49 [PATCH 0/7] some cleanups and uapi clarification for leases Daniel Vetter
2019-02-28 14:49 ` [PATCH 1/7] drm/leases: Drop object_id validation for negative ids Daniel Vetter
2019-03-14 7:54 ` Boris Brezillon
2019-03-29 4:46 ` Dave Airlie
2019-03-29 8:28 ` Daniel Vetter
2019-02-28 14:49 ` [PATCH 2/7] drm/lease: Drop recursive leads checks Daniel Vetter
2019-03-14 8:44 ` Boris Brezillon
2019-02-28 14:49 ` [PATCH 3/7] drm/leases: Don't init to 0 in drm_master_create Daniel Vetter
2019-03-14 7:56 ` Boris Brezillon
2019-03-29 4:47 ` Dave Airlie
2019-02-28 14:49 ` [PATCH 4/7] drm/lease: Check for lessor outside of locks Daniel Vetter
2019-03-14 8:07 ` Boris Brezillon
2019-04-03 1:33 ` Dave Airlie
2019-04-03 7:04 ` Daniel Vetter
2019-04-03 7:50 ` Boris Brezillon
2019-02-28 14:49 ` [PATCH 5/7] drm/lease: Make sure implicit planes are leased Daniel Vetter
2019-03-05 13:35 ` Sasha Levin
2019-02-28 14:49 ` [PATCH 6/7] drm/atomic: Wire file_priv through for property changes Daniel Vetter
2019-02-28 14:49 ` [PATCH 7/7] drm/atomic: -EACCESS for lease-denied crtc lookup Daniel Vetter
2019-03-14 8:58 ` [PATCH 0/7] some cleanups and uapi clarification for leases Boris Brezillon
2019-04-05 2:40 ` Dave Airlie [this message]
2019-04-24 9:31 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2019-02-28 17:00 Daniel Vetter
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='CAPM=9tz90rbbYCZS5377cEwM7MPyMjnW6CWWqdoAmai8fa+3ZQ@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).