From: Chris Wilson <chris@chris-wilson.co.uk>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Intel graphics driver community testing & development
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/3] drm/i915: Rename dev_priv->gtt to dev_priv->ggtt
Date: Fri, 18 Mar 2016 08:16:23 +0000 [thread overview]
Message-ID: <20160318081623.GM14143@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1458287590-23680-2-git-send-email-joonas.lahtinen@linux.intel.com>
On Fri, Mar 18, 2016 at 09:53:09AM +0200, Joonas Lahtinen wrote:
> Refer to Global GTT consistencly as GGTT, thus rename dev_priv->gtt
> to dev_priv->ggtt and struct i915_gtt to struct i915_ggtt.
Simple enough mechanical sed, and ggtt is a good name with ggtt vs ppgtt
nomenclature.
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
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-18 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 7:53 [PATCH 1/3] drm/i915/gtt: Reference mappable_end variable from pointer Joonas Lahtinen
2016-03-18 7:53 ` [PATCH 2/3] drm/i915: Rename dev_priv->gtt to dev_priv->ggtt Joonas Lahtinen
2016-03-18 8:16 ` Chris Wilson [this message]
2016-03-18 7:53 ` [PATCH 3/3] drm/i915/gtt: Clean up GGTT probing code Joonas Lahtinen
2016-03-18 8:19 ` Chris Wilson
2016-03-18 8:21 ` [PATCH 1/3] drm/i915/gtt: Reference mappable_end variable from pointer Chris Wilson
2016-03-18 8:54 ` Joonas Lahtinen
2016-03-21 9:35 ` Daniel Vetter
2016-03-21 9:39 ` Chris Wilson
2016-03-21 9:41 ` Daniel Vetter
2016-03-18 11:11 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] " 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=20160318081623.GM14143@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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.