From: Mark Adamenko <marusik.adamenko@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] usb: core: remove unnecessary goto in usb_create_newid_files()
Date: Wed, 4 Mar 2026 09:35:42 -0800 [thread overview]
Message-ID: <e8e05846-1af7-4cdf-8167-e566cf7db8c8@gmail.com> (raw)
In-Reply-To: <2026030412-trace-sneer-60bf@gregkh>
Thanks for responding,
I wasn't suggested by any tool. I was advised that if I want to become a
contributor, I should start by finding something small, so I came across
this file and found the goto. I understand it's not a big change, but
the kernel style guide says:
"The goto statement comes in handy when a function exits from multiple
locations and some common work such as cleanup has to be done. If there
is no cleanup needed then just return directly."
The original function only exits at the exit case and at the end of the
function, without extra cleanup.
On 3/4/26 08:11, Greg KH wrote:
> On Wed, Mar 04, 2026 at 07:58:12AM -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.
>
> Odd text wrapping :(
>
>>
>> Signed-off-by: Mark Adamenko <marusik.adamenko@gmail.com>
>> ---
>> v3: fix missing return statement at end of function
>> ---
>
> You forgot the other versions listed here :(
>
>> drivers/usb/core/driver.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> But first, why? There's no real need for this change, why make it at
> all? It follows the "standard" way of jumping to the end of the
> function to exit. What tool asked you to make this change?
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2026-03-04 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 15:58 [PATCH v3] usb: core: remove unnecessary goto in usb_create_newid_files() Mark Adamenko
2026-03-04 16:11 ` Greg KH
2026-03-04 17:35 ` Mark Adamenko [this message]
2026-03-04 20:46 ` Greg KH
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=e8e05846-1af7-4cdf-8167-e566cf7db8c8@gmail.com \
--to=marusik.adamenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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