Re: [PATCH v2] usb: core: remove unnecessary goto in usb_create_newid_files()

[Greg KH <gregkh@linuxfoundation.org>]

On Tue, Mar 03, 2026 at 10:46:46PM -0800, Mark Adamenko wrote:
> The goto to 'exit' only returns the already initialized variable
> 'error', which would be 0. At that point it could not yet be anything
> else. Replacing with an early return 0 removes the
> need for the label entirely.
> 
> Signed-off-by: Mark Adamenko <marusik.adamenko@gmail.com>
> ---
>  drivers/usb/core/driver.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c
> index 2574e65bc640..752ff84a8dc1 100644
> --- a/drivers/usb/core/driver.c
> +++ b/drivers/usb/core/driver.c
> @@ -186,7 +186,7 @@ static int usb_create_newid_files(struct usb_driver *usb_drv)
>  	int error = 0;
>  
>  	if (usb_drv->no_dynamic_id)
> -		goto exit;
> +		return 0;
>  
>  	if (usb_drv->probe != NULL) {
>  		error = driver_create_file(&usb_drv->driver,
> @@ -199,7 +199,7 @@ static int usb_create_newid_files(struct usb_driver *usb_drv)
>  						&driver_attr_new_id);
>  		}
>  	}
> -exit:
> +
>  	return error;
>  }
>  
> -- 
> 2.53.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:

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe 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