From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Make LRC (un)pinning work on context and engine
Date: Wed, 20 Jan 2016 13:55:22 +0000 [thread overview]
Message-ID: <20160120135522.GC16147@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1453297257-4707-1-git-send-email-tvrtko.ursulin@linux.intel.com>
On Wed, Jan 20, 2016 at 01:40:55PM +0000, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Previously intel_lr_context_(un)pin were operating on requests
> which is in conflict with their names.
>
> If we make them take a context and an engine, it makes the names
> make more sense and it also makes future fixes possible.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Nick Hoath <nicholas.hoath@intel.com>
Reviewed-by Chris Wilson <chris@chris-wilson.co.uk>
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-20 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 13:40 [PATCH 1/3] drm/i915: Make LRC (un)pinning work on context and engine Tvrtko Ursulin
2016-01-20 13:40 ` [PATCH 2/3] drm/i915: Make LRC pinning own a reference to the context Tvrtko Ursulin
2016-01-20 13:50 ` Chris Wilson
2016-01-20 13:40 ` [PATCH 3/3] drm/i915: Fix premature LRC unpin in GuC mode Tvrtko Ursulin
2016-01-20 13:55 ` Chris Wilson
2016-01-20 14:06 ` Tvrtko Ursulin
2016-01-20 14:18 ` Chris Wilson
2016-01-20 14:50 ` [PATCH v2] " Tvrtko Ursulin
2016-01-20 15:18 ` Chris Wilson
2016-01-20 14:21 ` [PATCH 3/3] " Nick Hoath
2016-01-20 13:55 ` Chris Wilson [this message]
2016-01-20 14:50 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Make LRC (un)pinning work on context and engine Patchwork
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=20160120135522.GC16147@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.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.