From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/6] drm/i915: Extract tile_row_size for fencing
Date: Tue, 10 Jan 2017 09:12:36 +0200 [thread overview]
Message-ID: <1484032356.3237.0.camel@linux.intel.com> (raw)
In-Reply-To: <20170109161613.11881-1-chris@chris-wilson.co.uk>
On ma, 2017-01-09 at 16:16 +0000, Chris Wilson wrote:
> Computing the tile row size of a tiled object (for use with fence
> registers) is repeated, so extract it to a common helper.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
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
prev parent reply other threads:[~2017-01-10 7:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 16:16 [PATCH 1/6] drm/i915: Extract tile_row_size for fencing Chris Wilson
2017-01-09 16:16 ` [PATCH 2/6] drm/i915: Align GGTT sizes to a fence tile row Chris Wilson
2017-01-09 16:16 ` [PATCH 3/6] drm/i915: Replace WARNs in fence register writes with extensive asserts Chris Wilson
2017-01-09 16:16 ` [PATCH 4/6] drm/i915: Store required fence size/alignment for GGTT vma Chris Wilson
2017-01-09 16:16 ` [PATCH 5/6] drm/i915: Remove the rounding down of the gen4+ fence region Chris Wilson
2017-01-09 16:16 ` [PATCH 6/6] drm/i915: Move ggtt fence/alignment to i915_gem_tiling.c Chris Wilson
2017-01-10 7:17 ` Joonas Lahtinen
2017-01-10 8:10 ` Chris Wilson
2017-01-09 17:23 ` ✓ Fi.CI.BAT: success for series starting with [1/6] drm/i915: Extract tile_row_size for fencing Patchwork
2017-01-10 9:35 ` Chris Wilson
2017-01-10 10:12 ` Tvrtko Ursulin
2017-01-10 10:22 ` Chris Wilson
2017-01-10 7:12 ` Joonas Lahtinen [this message]
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=1484032356.3237.0.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.