From: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: drm syncobjs - running out of tag lines
Date: Thu, 1 Jun 2017 11:06:38 +1000 [thread overview]
Message-ID: <20170601010643.28616-1-airlied@gmail.com> (raw)
Okay so Christian said he wanted lookup and replace split in the
amdgpu cs, this does this, and looks a bit cleaner, it required
changing some of the interfaces around on what is exported.
Dave.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2017-06-01 1:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 1:06 Dave Airlie [this message]
[not found] ` <20170601010643.28616-1-airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-01 1:06 ` [PATCH 1/5] drm: introduce sync objects (v4) Dave Airlie
[not found] ` <20170601010643.28616-2-airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-01 10:25 ` Chris Wilson
2017-06-01 1:06 ` [PATCH 2/5] drm/syncobj: add sync obj wait interface. (v4) Dave Airlie
2017-06-01 10:57 ` Chris Wilson
2017-06-01 1:06 ` [PATCH 4/5] amdgpu/cs: split out fence dependency checking Dave Airlie
2017-06-01 1:06 ` [PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v5) Dave Airlie
2017-06-15 3:59 ` Dave Airlie
[not found] ` <CAPM=9twtavgA+D+vgZYz7UagnjxX6pGFBBUycCs2ofGjhOcBrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-16 8:28 ` Christian König
[not found] ` <e8021851-d630-3cbd-40e2-58f83a366a29-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-06-17 1:23 ` Dave Airlie
2017-06-01 1:06 ` [PATCH 3/5] drm/syncobj: add sync_file interaction. (v1.2) Dave Airlie
[not found] ` <20170601010643.28616-4-airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-01 10:58 ` Chris Wilson
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=20170601010643.28616-1-airlied@gmail.com \
--to=airlied-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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).