From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Use BIT() for computing the engine's flag
Date: Mon, 27 Mar 2017 13:08:54 +0300 [thread overview]
Message-ID: <1490609334.3166.5.camel@linux.intel.com> (raw)
In-Reply-To: <20170324163540.31981-3-chris@chris-wilson.co.uk>
On pe, 2017-03-24 at 16:35 +0000, Chris Wilson wrote:
> Since the engine's flag is just the bit of its id, use BIT().
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-27 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 16:35 [PATCH 1/3] drm/i915: Fixup intel_write_status_page() for old CPUs without clflush Chris Wilson
2017-03-24 16:35 ` [PATCH 2/3] drm/i915: Remove unused intel_flush_status_page() Chris Wilson
2017-03-27 10:09 ` Joonas Lahtinen
2017-03-24 16:35 ` [PATCH 3/3] drm/i915: Use BIT() for computing the engine's flag Chris Wilson
2017-03-27 10:08 ` Joonas Lahtinen [this message]
2017-03-24 16:46 ` [PATCH 1/3] drm/i915: Fixup intel_write_status_page() for old CPUs without clflush Chris Wilson
2017-03-24 16:53 ` ✓ Fi.CI.BAT: success for series starting with [1/3] " Patchwork
2017-03-27 12:19 ` Chris Wilson
2017-03-24 19:05 ` [PATCH 1/3] " Ville Syrjälä
2017-03-24 20:53 ` Ville Syrjälä
2017-03-24 21:04 ` Chris Wilson
2017-03-24 21:12 ` Ville Syrjälä
2017-03-27 11:50 ` Mika Kuoppala
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=1490609334.3166.5.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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.