release_firmware() does its own tests for NULL pointers so there's no
need to explicitly test before calling it.

Signed-off-by: Jesper Juhl <j...@chaosbits.net>
---
 drivers/gpu/drm/radeon/radeon_cp.c |   12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/drivers/gpu/drm/radeon/radeon_cp.c 
b/drivers/gpu/drm/radeon/radeon_cp.c
index 0ebb7d4..ef67e18 100644
--- a/drivers/gpu/drm/radeon/radeon_cp.c
+++ b/drivers/gpu/drm/radeon/radeon_cp.c
@@ -1827,14 +1827,10 @@ void radeon_do_release(struct drm_device * dev)
                        r600_do_cleanup_cp(dev);
                else
                        radeon_do_cleanup_cp(dev);
-               if (dev_priv->me_fw) {
-                       release_firmware(dev_priv->me_fw);
-                       dev_priv->me_fw = NULL;
-               }
-               if (dev_priv->pfp_fw) {
-                       release_firmware(dev_priv->pfp_fw);
-                       dev_priv->pfp_fw = NULL;
-               }
+               release_firmware(dev_priv->me_fw);
+               dev_priv->me_fw = NULL;
+               release_firmware(dev_priv->pfp_fw);
+               dev_priv->pfp_fw = NULL;
        }
 }
 
-- 
1.7.10


-- 
Jesper Juhl <j...@chaosbits.net>       http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Reply via email to