From: Daniel Vetter Date: Mon, 15 Sep 2014 12:55:22 +0000 (+0200) Subject: drm/i915: Clarify event_lock locking, process context X-Git-Tag: omap-for-v3.19/fixes-rc1~80^2~79^2~52 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5e2d7afcfefa7cda3f341ce78523bb9b0acdbacf;p=pandora-kernel.git drm/i915: Clarify event_lock locking, process context It's good practice to use the more specific versions for irq save spinlocks both as executable documentation and to enforce saner design. The _irqsave version really should only be used if the calling context is unknown and there's a good reason to call a function from all kinds of places. This is the first step whice replaces all occurances of _irqsave in process context with the simpler irq disable/enable variants. We don't have any funky spinlock nesting going on, especially since the event_lock is the outermost of the irq/vblank related spinlocks. Reviewed-by: Jesse Barnes Signed-off-by: Daniel Vetter --- Reading git-diff-tree failed