public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kushagra Verma <kushagra765@outlook.com>
Cc: balbi@kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB / dwc3: remove a possible unnecessary 'out of memory' message
Date: Sun, 1 May 2022 17:39:19 +0200	[thread overview]
Message-ID: <Ym6pp/O1fpneA5ZW@kroah.com> (raw)
In-Reply-To: <SI2PR01MB3929F20DA02363BD6A88657DF8FE9@SI2PR01MB3929.apcprd01.prod.exchangelabs.com>

On Sun, May 01, 2022 at 09:01:36PM +0530, Kushagra Verma wrote:
> This patch removes a possible unnecessary out of memory message from
> core.c
> as reported by checkpatch.pl:
>    WARNING: Possible unnecessary 'out of memory' message
> 
> Signed-off-by: Kushagra Verma <kushagra765@outlook.com>
> ---
>  drivers/usb/dwc3/core.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 25c686a752b0..4ee787de2956 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -844,10 +844,8 @@ static void dwc3_set_incr_burst_type(struct dwc3
> *dwc)
>  		return;
>  
>  	vals = kcalloc(ntype, sizeof(u32), GFP_KERNEL);
> -	if (!vals) {
> -		dev_err(dev, "Error to get memory\n");
> +	if (!vals)
>  		return;
> -	}
>  
>  	/* Get INCR burst type, and parse it */
>  	ret = device_property_read_u32_array(dev,
> -- 
> 2.32.0
> 
> 
> 

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:

- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
  and can not be applied.  Please read the file,
  Documentation/email-clients.txt in order to fix this.

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

  reply	other threads:[~2022-05-01 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 15:31 [PATCH] USB / dwc3: remove a possible unnecessary 'out of memory' message Kushagra Verma
2022-05-01 15:39 ` Greg KH [this message]
2022-05-01 16:50   ` Joe Perches
2022-05-01 17:09     ` Greg KH
2022-05-01 17:20       ` Joe Perches
  -- strict thread matches above, loose matches on Subject: below --
2022-05-02  9:07 Kushagra Verma

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=Ym6pp/O1fpneA5ZW@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@kernel.org \
    --cc=kushagra765@outlook.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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