From: Eric Anholt <eric@anholt.net>
Cc: airlied@linux.ie, linux-rpi-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org,
Stefan Schake <stschake@gmail.com>
Subject: Re: [PATCH v2 0/3] drm/vc4: Syncobj import export
Date: Mon, 30 Apr 2018 16:05:50 -0700 [thread overview]
Message-ID: <87sh7c70s1.fsf@anholt.net> (raw)
In-Reply-To: <1524607427-12876-1-git-send-email-stschake@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]
Stefan Schake <stschake@gmail.com> writes:
> v2 drops the extra syncobj parameter and gets rid of the submit flags
> since 0 is never a valid syncobj handle.
>
> This series allows userspace to submit syncobj handles for importing
> a fence to wait on or exporting the job fence as part of submission.
>
> The primary use of this is to enable native fence fd support in Mesa.
> Userspace implementation is under review and available here:
This series was a joy to read. I've reviewed and pushed it to
drm-misc-next, and we can land the Mesa side once it's made its way to
drm-next.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-04-30 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 22:03 [PATCH v2 0/3] drm/vc4: Syncobj import export Stefan Schake
2018-04-24 22:03 ` [PATCH v2 1/3] drm/vc4: Syncobj import support Stefan Schake
2018-04-24 22:03 ` [PATCH v2 2/3] drm/vc4: Export fence through syncobj Stefan Schake
2018-04-24 22:03 ` [PATCH v2 3/3] drm/vc4: Enable syncobj support Stefan Schake
2018-04-30 23:05 ` Eric Anholt [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=87sh7c70s1.fsf@anholt.net \
--to=eric@anholt.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stschake@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.