From: Greg KH <gregkh@linuxfoundation.org>
To: Pawel Laszczak <pawell@cadence.com>
Cc: peter.chen@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: cdnsp: remove not used variables
Date: Tue, 11 Jan 2022 10:12:38 +0100 [thread overview]
Message-ID: <Yd1KBiRB/ByZ2Kx1@kroah.com> (raw)
In-Reply-To: <20220111085934.44844-1-pawell@gli-login.cadence.com>
On Tue, Jan 11, 2022 at 09:59:34AM +0100, Pawel Laszczak wrote:
> From: Pawel Laszczak <pawell@cadence.com>
>
> Patch removes not used variables:
> - ret from cdnsp_decode_trb function
> - temp_64 from cdnsp_run function
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Pawel Laszczak <pawell@cadence.com>
> ---
> drivers/usb/cdns3/cdnsp-debug.h | 287 +++++++++++++++----------------
> drivers/usb/cdns3/cdnsp-gadget.c | 3 -
> 2 files changed, 138 insertions(+), 152 deletions(-)
>
> diff --git a/drivers/usb/cdns3/cdnsp-debug.h b/drivers/usb/cdns3/cdnsp-debug.h
> index a8776df2d4e0..29f3cf7ddbaa 100644
> --- a/drivers/usb/cdns3/cdnsp-debug.h
> +++ b/drivers/usb/cdns3/cdnsp-debug.h
> @@ -182,206 +182,195 @@ static inline const char *cdnsp_decode_trb(char *str, size_t size, u32 field0,
> int ep_id = TRB_TO_EP_INDEX(field3) - 1;
> int type = TRB_FIELD_TO_TYPE(field3);
> unsigned int ep_num;
> - int ret = 0;
Please fix this function to properly handle the ret value, as I think it
should be checked, right?
> --- a/drivers/usb/cdns3/cdnsp-gadget.c
> +++ b/drivers/usb/cdns3/cdnsp-gadget.c
> @@ -1243,12 +1243,9 @@ static int cdnsp_run(struct cdnsp_device *pdev,
> enum usb_device_speed speed)
> {
> u32 fs_speed = 0;
> - u64 temp_64;
> u32 temp;
> int ret;
>
> - temp_64 = cdnsp_read_64(&pdev->ir_set->erst_dequeue);
> - temp_64 &= ~ERST_PTR_MASK;
> temp = readl(&pdev->ir_set->irq_control);
> temp &= ~IMOD_INTERVAL_MASK;
> temp |= ((IMOD_DEFAULT_INTERVAL / 250) & IMOD_INTERVAL_MASK);
> --
> 2.25.1
>
A separate patch for this.
Also, are you SURE this is ok to do? Did you check it on the hardware
that a read is not needed here for it to work properly?
This type of "warning" is horrible for dealing with hardware devices,
always treat it as incorrect unless you can prove otherwise.
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-11 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 8:59 [PATCH] usb: cdnsp: remove not used variables Pawel Laszczak
2022-01-11 9:12 ` Greg KH [this message]
2022-01-11 10:38 ` Pawel Laszczak
2022-01-11 11:13 ` Greg KH
2022-01-12 13:00 ` Peter Chen
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=Yd1KBiRB/ByZ2Kx1@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=peter.chen@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