Smatch complains about the recent locking changes in
intel_setup_overlay() that it unlocks twice on an error path. I was
also curious if we shouldn't call i915_gem_object_unpin() on that
error path. I don't know the drm code well enough to know about
unpinning so I'm sending this bug report inste
On Thu, 23 Jun 2011 21:06:16 +0300, Dan Carpenter wrote:
> Smatch complains about the recent locking changes in
> intel_setup_overlay() that it unlocks twice on an error path. I was
> also curious if we shouldn't call i915_gem_object_unpin() on that
> error path. I don't know the drm code well e
On Thu, 23 Jun 2011 21:06:16 +0300, Dan Carpenter wrote:
> Smatch complains about the recent locking changes in
> intel_setup_overlay() that it unlocks twice on an error path. I was
> also curious if we shouldn't call i915_gem_object_unpin() on that
> error path. I don't know the drm code well e
Smatch complains about the recent locking changes in
intel_setup_overlay() that it unlocks twice on an error path. I was
also curious if we shouldn't call i915_gem_object_unpin() on that
error path. I don't know the drm code well enough to know about
unpinning so I'm sending this bug report inste
