From: Conor Dooley <conor@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Okan Tumuklu <okantumukluu@gmail.com>,
shuah@kernel.org, linux-kernel@vger.kernel.org, krzk@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] Update core.c
Date: Mon, 30 Sep 2024 23:20:45 +0100 [thread overview]
Message-ID: <20240930-plant-brim-b8178db46885@spud> (raw)
In-Reply-To: <7dcaa550-4c12-4c2e-9ae2-794c87048ea9@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 2817 bytes --]
On Mon, Sep 30, 2024 at 04:12:41PM -0600, Shuah Khan wrote:
> On 9/30/24 16:06, Okan Tumuklu wrote:
> > From: Okan Tümüklü <117488504+Okan-tumuklu@users.noreply.github.com>
> >
> > 1:The control flow was simplified by using else if statements instead of goto structure.
> >
> > 2:Error conditions are handled more clearly.
> >
> > 3:The device_unlock call at the end of the function is guaranteed in all cases.
>
> Write a paragraph - don't use bullet lists.
>
> Please refer to submitting patches for details on how to
> write shortlogs and change logs.
>
> "Update core.c" with what? Write a better short log.
>
> Why do you this 117488504+Okan-tumuklu@users.noreply.github.com
> in the list? It will complain every time someone responds
> to this thread. This is not how patches are sent. Refer to
> documents in the kernel repo on how to send patches.
>
> You are missing net maintainers and mailing lists.
>
> Include all reviewers - run get_maintainers.pl
And consider whether the patch is a trip up the garden path, or
actually worthwhile.
Why would if/else be better than a goto?
What's unclear about the current error handling?
In what case is the device_unlock() call missed?
Maybe there's some value in using the scoped cleanup here (do netdev
folks even want scoped cleanup?), but this patch may not be worth the
time spent improving it. +CC Krzk and netdev, before more time is
potentially wasted here.
Cheers,
Conor.
>
> > ---
> > net/nfc/core.c | 28 ++++++++++------------------
> > 1 file changed, 10 insertions(+), 18 deletions(-)
> >
> > diff --git a/net/nfc/core.c b/net/nfc/core.c
> > index e58dc6405054..4e8f01145c37 100644
> > --- a/net/nfc/core.c
> > +++ b/net/nfc/core.c
> > @@ -40,27 +40,19 @@ int nfc_fw_download(struct nfc_dev *dev, const char *firmware_name)
> > if (dev->shutting_down) {
> > rc = -ENODEV;
> > - goto error;
> > - }
> > -
> > - if (dev->dev_up) {
> > + }else if (dev->dev_up) {
> > rc = -EBUSY;
> > - goto error;
> > - }
>
> Did you run checkpack script on this patch? There are a few
> coding style errors.
>
> > -
> > - if (!dev->ops->fw_download) {
> > + }else if (!dev->ops->fw_download) {
> > rc = -EOPNOTSUPP;
> > - goto error;
> > - }
> > -
> > - dev->fw_download_in_progress = true;
> > - rc = dev->ops->fw_download(dev, firmware_name);
> > - if (rc)
> > - dev->fw_download_in_progress = false;
> > + }else{
> > + dev->fw_download_in_progress = true;
> > + rc = dev->ops->fw_download(dev, firmware_name);
> > + if (rc)
> > + dev->fw_download_in_progress = false;
> > + }
> > -error:
> > - device_unlock(&dev->dev);
> > - return rc;
> > + device_unlock(&dev->dev);
> > + return rc;
> > }
> > /**
>
> thanks,
> -- Shuah
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2024-09-30 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240930220649.6954-1-okantumukluu@gmail.com>
[not found] ` <7dcaa550-4c12-4c2e-9ae2-794c87048ea9@linuxfoundation.org>
2024-09-30 22:20 ` Conor Dooley [this message]
2024-10-02 13:27 ` [PATCH] Update core.c Jakub Kicinski
2024-10-02 15:26 ` Shuah Khan
2024-10-02 22:21 ` Al Viro
2024-10-02 23:41 ` Jakub Kicinski
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=20240930-plant-brim-b8178db46885@spud \
--to=conor@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=okantumukluu@gmail.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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