All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/i915: Make LRC (un)pinning work on context and engine
Date: Thu, 28 Jan 2016 10:31:37 +0000	[thread overview]
Message-ID: <56A9EE09.5050009@linux.intel.com> (raw)
In-Reply-To: <1453976997-25424-1-git-send-email-tvrtko.ursulin@linux.intel.com>


On 28/01/16 10:29, 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.
>
> v2: Rebase for default_context/kernel_context change.

Series re-sent for CI only.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-01-28 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 10:29 [PATCH 1/4] drm/i915: Make LRC (un)pinning work on context and engine Tvrtko Ursulin
2016-01-28 10:29 ` [PATCH 2/4] drm/i915: Make LRC pinning own a reference to the context Tvrtko Ursulin
2016-01-28 10:29 ` [PATCH 3/4] drm/i915: Extract context unpinning to its own function Tvrtko Ursulin
2016-01-28 10:29 ` [PATCH 4/4] drm/i915: Fix premature LRC unpin in GuC mode Tvrtko Ursulin
2016-01-28 10:31 ` Tvrtko Ursulin [this message]
2016-01-28 17:26 ` ✗ Fi.CI.BAT: failure for series starting with [1/4] drm/i915: Make LRC (un)pinning work on context and engine Patchwork
2016-01-28 17:30   ` Tvrtko Ursulin

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=56A9EE09.5050009@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@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 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.