mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Andrej Krutak <dev@andree.sk>,
	kbuild-all@01.org, alsa-devel@alsa-project.org,
	Jaroslav Kysela <perex@perex.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: line6: fix ifnullfree.cocci warnings
Date: Tue, 20 Sep 2016 12:54:20 +0200	[thread overview]
Message-ID: <s5h4m5au9ib.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160920001013.GA15786@lkp-hsx03.lkp.intel.com>

On Tue, 20 Sep 2016 02:10:13 +0200,
kbuild test robot wrote:
> 
> sound/usb/line6/driver.c:484:2-7: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid passing NULL values.
> 
>  NULL check before some freeing functions is not needed.
> 
>  Based on checkpatch warning
>  "kfree(NULL) is safe this check is probably not required"
>  and kfreeaddr.cocci by Julia Lawall.
> 
> Generated by: scripts/coccinelle/free/ifnullfree.cocci
> 
> CC: Andrej Krutak <dev@andree.sk>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>

Applied, thanks.


Takashi


> ---
> 
>  driver.c |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> --- a/sound/usb/line6/driver.c
> +++ b/sound/usb/line6/driver.c
> @@ -480,8 +480,7 @@ static void line6_destruct(struct snd_ca
>  	/* Free buffer memory first. We cannot depend on the existence of private
>  	 * data from the (podhd) module, it may be gone already during this call
>  	 */
> -	if (line6->buffer_message)
> -		kfree(line6->buffer_message);
> +	kfree(line6->buffer_message);
>  
>  	kfree(line6->buffer_listen);
>  
> 

      reply	other threads:[~2016-09-20 10:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201609200807.amTCnbAm%fengguang.wu@intel.com>
2016-09-20  0:10 ` kbuild test robot
2016-09-20 10:54   ` Takashi Iwai [this message]

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=s5h4m5au9ib.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=dev@andree.sk \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    /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

all inboxes | Powered by JetHome®