Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: It's its!
Date: Fri, 30 Aug 2013 15:26:30 -0700	[thread overview]
Message-ID: <20130830222630.GD7546@bwidawsk.net> (raw)
In-Reply-To: <1377870026-9790-1-git-send-email-damien.lespiau@intel.com>

On Fri, Aug 30, 2013 at 02:40:26PM +0100, Damien Lespiau wrote:
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_gem_context.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index 403309c..e038513 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -73,7 +73,7 @@
>   *
>   * There are two confusing terms used above:
>   *  The "current context" means the context which is currently running on the
> - *  GPU. The GPU has loaded it's state already and has stored away the gtt
> + *  GPU. The GPU has loaded its state already and has stored away the gtt
>   *  offset of the BO. The GPU is not actively referencing the data at this
>   *  offset, but it will on the next context switch. The only way to avoid this
>   *  is to do a GPU reset.

Acked-by: Ben Widawsky <ben@bwidawsk.net>

By the way, I plan to rewrite a lot of this once we land full PPGTT.

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2013-08-30 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 13:40 [PATCH] drm/i915: It's its! Damien Lespiau
2013-08-30 22:26 ` Ben Widawsky [this message]
2013-09-02  6:23   ` Daniel Vetter

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=20130830222630.GD7546@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=damien.lespiau@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox