From: Daniel Vetter <daniel@ffwll.ch>
To: Julia Lawall <Julia.Lawall@lip6.fr>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
sergey.senozhatsky@gmail.com,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 32/39] drm: i915: drop null test before destroy functions
Date: Wed, 30 Sep 2015 10:44:18 +0200 [thread overview]
Message-ID: <20150930084418.GC3383@phenom.ffwll.local> (raw)
In-Reply-To: <1442146532-9100-33-git-send-email-Julia.Lawall@lip6.fr>
On Sun, Sep 13, 2015 at 02:15:25PM +0200, Julia Lawall wrote:
> Remove unneeded NULL test.
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@ expression x; @@
> -if (x != NULL)
> \(kmem_cache_destroy\|mempool_destroy\|dma_pool_destroy\)(x);
> // </smpl>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Queued for -next, thanks for the patch.
-Daniel
>
> ---
> drivers/gpu/drm/i915/i915_dma.c | 19 ++++++-------------
> 1 file changed, 6 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
> index ab37d11..1dc7c21 100644
> --- a/drivers/gpu/drm/i915/i915_dma.c
> +++ b/drivers/gpu/drm/i915/i915_dma.c
> @@ -1059,12 +1059,9 @@ out_freecsr:
> put_bridge:
> pci_dev_put(dev_priv->bridge_dev);
> free_priv:
> - if (dev_priv->requests)
> - kmem_cache_destroy(dev_priv->requests);
> - if (dev_priv->vmas)
> - kmem_cache_destroy(dev_priv->vmas);
> - if (dev_priv->objects)
> - kmem_cache_destroy(dev_priv->objects);
> + kmem_cache_destroy(dev_priv->requests);
> + kmem_cache_destroy(dev_priv->vmas);
> + kmem_cache_destroy(dev_priv->objects);
> kfree(dev_priv);
> return ret;
> }
> @@ -1150,13 +1147,9 @@ int i915_driver_unload(struct drm_device *dev)
> if (dev_priv->regs != NULL)
> pci_iounmap(dev->pdev, dev_priv->regs);
>
> - if (dev_priv->requests)
> - kmem_cache_destroy(dev_priv->requests);
> - if (dev_priv->vmas)
> - kmem_cache_destroy(dev_priv->vmas);
> - if (dev_priv->objects)
> - kmem_cache_destroy(dev_priv->objects);
> -
> + kmem_cache_destroy(dev_priv->requests);
> + kmem_cache_destroy(dev_priv->vmas);
> + kmem_cache_destroy(dev_priv->objects);
> pci_dev_put(dev_priv->bridge_dev);
> kfree(dev_priv);
>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-30 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 12:14 [PATCH 00/39] drop null test before destroy functions Julia Lawall
2015-09-13 12:15 ` [PATCH 32/39] drm: i915: " Julia Lawall
2015-09-30 8:44 ` Daniel Vetter [this message]
2015-09-14 11:55 ` [PATCH 00/39] " SF Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150930084418.GC3383@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Julia.Lawall@lip6.fr \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox