From: Greg KH <gregkh@linuxfoundation.org>
To: Atul Kumar Pant <atulpant.linux@gmail.com>
Cc: richard.leitner@linux.dev, wsa+renesas@sang-engineering.com,
mhocko@suse.com, surenb@google.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, shuah@kernel.org
Subject: Re: [PATCH v1] drivers: usb: Removes use of assignment in if condition
Date: Tue, 15 Aug 2023 23:07:02 +0200 [thread overview]
Message-ID: <2023081550-absurd-sprint-65e5@gregkh> (raw)
In-Reply-To: <20230815204141.51972-1-atulpant.linux@gmail.com>
On Wed, Aug 16, 2023 at 02:11:41AM +0530, Atul Kumar Pant wrote:
> This patch fixes following checkpatch.pl issue:
> ERROR: do not use assignment in if condition
>
> Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
> ---
> drivers/usb/core/devio.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
> index e501a03d6c70..56899fed6bd4 100644
> --- a/drivers/usb/core/devio.c
> +++ b/drivers/usb/core/devio.c
> @@ -2333,9 +2333,10 @@ static int proc_ioctl(struct usb_dev_state *ps, struct usbdevfs_ioctl *ctl)
> }
> }
>
> + intf = usb_ifnum_to_if(ps->dev, ctl->ifno);
> if (ps->dev->state != USB_STATE_CONFIGURED)
> retval = -EHOSTUNREACH;
> - else if (!(intf = usb_ifnum_to_if(ps->dev, ctl->ifno)))
> + else if (!intf)
Did you mean to change the logic here by doing the calculation always?
Does that change functionality?
The existing code is fine, running checkpatch on code outside of
drivers/staging/ or on new patches you are writing, is generally
discouraged as the code usually is older than checkpatch is :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-15 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 20:41 [PATCH v1] drivers: usb: Removes use of assignment in if condition Atul Kumar Pant
2023-08-15 21:07 ` Greg KH [this message]
2023-08-16 2:52 ` Atul Kumar Pant
2023-08-16 14:43 ` Greg KH
2023-08-16 3:43 ` Atul Kumar Pant
2023-08-16 14:42 ` 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=2023081550-absurd-sprint-65e5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=atulpant.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=richard.leitner@linux.dev \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=wsa+renesas@sang-engineering.com \
/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