From: Nathan Chancellor <natechancellor@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <balbi@kernel.org>,
Ashwini Pahuja <ashwini.linux@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete
Date: Thu, 20 Feb 2020 21:57:40 -0700 [thread overview]
Message-ID: <20200221045740.GA43417@ubuntu-m2-xlarge-x86> (raw)
In-Reply-To: <20191023002014.22571-1-natechancellor@gmail.com>
I know it has been a while but ping?
On Tue, Oct 22, 2019 at 05:20:15PM -0700, Nathan Chancellor wrote:
> When building with Clang + -Wtautological-pointer-compare:
>
> drivers/usb/gadget/udc/bdc/bdc_ep.c:543:28: warning: comparison of
> address of 'req->queue' equal to a null pointer is always false
> [-Wtautological-pointer-compare]
> if (req == NULL || &req->queue == NULL || &req->usb_req == NULL)
> ~~~~~^~~~~ ~~~~
> drivers/usb/gadget/udc/bdc/bdc_ep.c:543:51: warning: comparison of
> address of 'req->usb_req' equal to a null pointer is always false
> [-Wtautological-pointer-compare]
> if (req == NULL || &req->queue == NULL || &req->usb_req == NULL)
> ~~~~~^~~~~~~ ~~~~
> 2 warnings generated.
>
> As it notes, these statements will always evaluate to false so remove
> them.
>
> Fixes: efed421a94e6 ("usb: gadget: Add UDC driver for Broadcom USB3.0 device controller IP BDC")
> Link: https://github.com/ClangBuiltLinux/linux/issues/749
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
>
> Note: I am not sure if these checks were intended to check if the
> contents of these arrays were NULL or if there should be some other
> checks in lieu of these; I am not familiar with the USB subsystem to
> answer this but I will happily respin the patch if this is not correct.
>
> drivers/usb/gadget/udc/bdc/bdc_ep.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/gadget/udc/bdc/bdc_ep.c b/drivers/usb/gadget/udc/bdc/bdc_ep.c
> index a4d9b5e1e50e..d49c6dc1082d 100644
> --- a/drivers/usb/gadget/udc/bdc/bdc_ep.c
> +++ b/drivers/usb/gadget/udc/bdc/bdc_ep.c
> @@ -540,7 +540,7 @@ static void bdc_req_complete(struct bdc_ep *ep, struct bdc_req *req,
> {
> struct bdc *bdc = ep->bdc;
>
> - if (req == NULL || &req->queue == NULL || &req->usb_req == NULL)
> + if (req == NULL)
> return;
>
> dev_dbg(bdc->dev, "%s ep:%s status:%d\n", __func__, ep->name, status);
> --
> 2.23.0
>
next prev parent reply other threads:[~2020-02-21 4:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 0:20 [PATCH] usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete Nathan Chancellor
2020-02-21 4:57 ` Nathan Chancellor [this message]
2020-02-24 21:42 ` Nick Desaulniers
2020-03-26 19:58 ` Nathan Chancellor
2020-03-28 8:35 ` Felipe Balbi
2020-03-29 1:12 ` [PATCH RESEND] " Nathan Chancellor
2020-03-29 7:43 ` Felipe Balbi
2020-03-29 14:47 ` Nathan Chancellor
2020-03-29 16:43 ` Felipe Balbi
2020-03-30 6:08 ` Greg Kroah-Hartman
2020-03-30 7:22 ` Felipe Balbi
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=20200221045740.GA43417@ubuntu-m2-xlarge-x86 \
--to=natechancellor@gmail.com \
--cc=ashwini.linux@gmail.com \
--cc=balbi@kernel.org \
--cc=clang-built-linux@googlegroups.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;
as well as URLs for NNTP newsgroup(s).