From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Initialize legacy semaphores from engine hw id indexed array
Date: Thu, 11 Aug 2016 12:06:53 +0100 [thread overview]
Message-ID: <57AC5C4D.10104@linux.intel.com> (raw)
In-Reply-To: <20160811105357.GH12148@nuc-i3427.alporthouse.com>
On 11/08/16 11:53, Chris Wilson wrote:
> On Thu, Aug 11, 2016 at 11:43:38AM +0100, Tvrtko Ursulin wrote:
>> +#define I915_GEN6_SEMA_ENGINES 4
>
> #define GEN6_SEMAPHORE_LAST VECS_HW
>
> In theory, I915 and GEN6 are part of the same prefix class.
>
> With that change and follow through for the inclusive test,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Sent v2. Please can you check that it looks like you wanted there, since
I did not carry this rb just in case?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-11 11:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 10:43 [PATCH 0/2] Shrink and lock the size static gen6 semaphore init array Tvrtko Ursulin
2016-08-11 10:43 ` [PATCH 1/2] drm/i915: Add enum for hardware engine identifiers Tvrtko Ursulin
2016-08-11 10:43 ` [PATCH 2/2] drm/i915: Initialize legacy semaphores from engine hw id indexed array Tvrtko Ursulin
2016-08-11 10:53 ` Chris Wilson
2016-08-11 11:05 ` [PATCH v2] " Tvrtko Ursulin
2016-08-11 11:20 ` Chris Wilson
2016-08-11 14:45 ` Tvrtko Ursulin
2016-08-11 14:50 ` [PATCH v3] " Tvrtko Ursulin
2016-08-11 15:46 ` Chris Wilson
2016-08-11 11:06 ` Tvrtko Ursulin [this message]
2016-08-11 11:58 ` ✗ Ro.CI.BAT: failure for Shrink and lock the size static gen6 semaphore init array (rev2) Patchwork
2016-08-11 15:31 ` ✗ Ro.CI.BAT: failure for Shrink and lock the size static gen6 semaphore init array (rev3) 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=57AC5C4D.10104@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
/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