All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Archana <craechal@gmail.com>
Cc: drv@mailo.com, linux-staging@lists.linux.dev
Subject: Re: [PATCH 1/2] staging: wlan-ng: remove unnecessary kfree statements
Date: Sat, 11 Mar 2023 08:40:50 +0100	[thread overview]
Message-ID: <ZAwwgsZd+2OAD1DM@kroah.com> (raw)
In-Reply-To: <20230310205917.2161-1-craechal@gmail.com>

On Fri, Mar 10, 2023 at 08:59:16PM +0000, Archana wrote:
> The function uses goto free_result in rest of its implementation.
> 
> Signed-off-by: Archana <craechal@gmail.com>
> ---
>  drivers/staging/wlan-ng/prism2fw.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/wlan-ng/prism2fw.c b/drivers/staging/wlan-ng/prism2fw.c
> index 02a2191d5c4d..98ed9bb9192c 100644
> --- a/drivers/staging/wlan-ng/prism2fw.c
> +++ b/drivers/staging/wlan-ng/prism2fw.c
> @@ -1008,12 +1008,11 @@ static int writeimage(struct wlandevice *wlandev, struct imgchunk *fchunk,
>  	rstmsg = kzalloc(sizeof(*rstmsg), GFP_KERNEL);
>  	rwrmsg = kzalloc(sizeof(*rwrmsg), GFP_KERNEL);
>  	if (!rstmsg || !rwrmsg) {
> -		kfree(rstmsg);
> -		kfree(rwrmsg);
>  		netdev_err(wlandev->netdev,
>  			   "%s: no memory for firmware download, aborting download\n",
>  			   __func__);
> -		return -ENOMEM;
> +		result = -ENOMEM;
> +		goto free_result;
>  	}
>  
>  	/* Initialize the messages */
> -- 
> 2.34.1
> 
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what is needed in
  order to properly describe the change.

- It looks like you did not use your "real" name for the patch on either
  the Signed-off-by: line, or the From: line (both of which have to
  match).  Please read the kernel file,
  Documentation/process/submitting-patches.rst for how to do this
  correctly.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

  parent reply	other threads:[~2023-03-11  7:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 20:59 [PATCH 1/2] staging: wlan-ng: remove unnecessary kfree statements Archana
2023-03-10 20:59 ` [PATCH 2/2] staging: wlan-ng: remove else statement Archana
2023-03-11  4:34   ` Dan Carpenter
2023-03-11  4:58     ` Dan Carpenter
2023-03-11  7:39       ` Greg KH
2023-03-11 12:12         ` [PATCH v2 1/2] staging: wlan-ng: small cleanup in writeimage() Archana
2023-03-11 12:12           ` [PATCH v2 2/2] staging: wlan-ng: small cleanup in plugimage() Archana
2023-03-11 12:37           ` [PATCH v2 1/2] staging: wlan-ng: small cleanup in writeimage() Dan Carpenter
2023-03-11 12:45         ` [PATCH 2/2] staging: wlan-ng: remove else statement Archana
2023-03-11  7:40 ` Greg KH [this message]
2023-03-16 11:19   ` [PATCH 1/2] staging: wlan-ng: remove unnecessary kfree statements Archana
2023-03-16 11:27   ` Archana

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=ZAwwgsZd+2OAD1DM@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=craechal@gmail.com \
    --cc=drv@mailo.com \
    --cc=linux-staging@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.