On Fri, Aug 30, 2013 at 03:26:30PM -0700, Ben Widawsky wrote: > On Fri, Aug 30, 2013 at 02:40:26PM +0100, Damien Lespiau wrote: > > Signed-off-by: Damien Lespiau <damien.lespiau@xxxxxxxxx> > > --- > > 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@xxxxxxxxxxxx> Queued for -next, thanks for the patch. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
