drm/i915: Correct typo for __i915_gem_active_get_rcu in a comment
authorChris Wilson <chris@chris-wilson.co.uk>
Tue, 9 Aug 2016 16:03:22 +0000 (17:03 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Tue, 9 Aug 2016 16:17:56 +0000 (17:17 +0100)
I mistyped and added an extra _request_ to __i915_gem_active_get_rcu()
Also, the same happened to another comment for i915_gem_active_get_rcu()

Reported-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1470758602-1338-1-git-send-email-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/i915_gem_request.c
drivers/gpu/drm/i915/intel_ringbuffer.h

index 06d1267e733d3721ae022743f9c4256385768fc0..76314e527cfd75ccf0204ebe15ffe90244e8ace0 100644 (file)
@@ -360,7 +360,7 @@ i915_gem_request_alloc(struct intel_engine_cs *engine,
         * We use RCU to look up requests in flight. The lookups may
         * race with the request being allocated from the slab freelist.
         * That is the request we are writing to here, may be in the process
-        * of being read by __i915_gem_active_get_request_rcu(). As such,
+        * of being read by __i915_gem_active_get_rcu(). As such,
         * we have to be very careful when overwriting the contents. During
         * the RCU lookup, we change chase the request->engine pointer,
         * read the request->fence.seqno and increment the reference count.
index 43e545e443521c87e4120021f0536a371bfffd8d..bf9a6e56e7191c28e59ed628c9d7b5ba6036006a 100644 (file)
@@ -310,7 +310,7 @@ struct intel_engine_cs {
 
        /* An RCU guarded pointer to the last request. No reference is
         * held to the request, users must carefully acquire a reference to
-        * the request using i915_gem_active_get_request_rcu(), or hold the
+        * the request using i915_gem_active_get_rcu(), or hold the
         * struct_mutex.
         */
        struct i915_gem_active last_request;