From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Danila Chernetsov <listdansp@mail.ru>
Cc: stable@vger.kernel.org, Bin Liu <b-liu@ti.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, Sergey Shtylyov <s.shtylyov@omp.ru>
Subject: Re: [PATCH 5.10 1/1] usb: musb: core: drop redundant checks
Date: Tue, 14 Mar 2023 18:08:44 +0100 [thread overview]
Message-ID: <ZBCqHJz8zYeXQ3Q7@kroah.com> (raw)
In-Reply-To: <20230314170113.11968-2-listdansp@mail.ru>
On Tue, Mar 14, 2023 at 05:01:13PM +0000, Danila Chernetsov wrote:
> From: Sergey Shtylyov <s.shtylyov@omp.ru>
>
> commit b0ec7e55fce65f125bd1d7f02e2dc4de62abee34 upstream.
Nit, trailing whitespace, please fix your editor to show this up easier.
>
> In musb_{save|restore}_context() the expression '&musb->endpoints[i]' just
> cannot be NULL, so the checks have no sense at all -- after dropping them,
> the local variables 'hw_ep' are no longer necessary, so drop them as well.
>
> Found by Linux Verification Center (linuxtesting.org) with the SVACE static
> analysis tool.
>
> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
> Link: https://lore.kernel.org/r/3f8f60d9-f1b5-6b2c-1222-39b156151a22@omp.ru
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Danila Chernetsov <listdansp@mail.ru>
> ---
> drivers/usb/musb/musb_core.c | 16 ++--------------
> 1 file changed, 2 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
> index 4c8f0112481f..605f5cc0f18b 100644
> --- a/drivers/usb/musb/musb_core.c
> +++ b/drivers/usb/musb/musb_core.c
> @@ -2673,13 +2673,7 @@ static void musb_save_context(struct musb *musb)
> musb->context.devctl = musb_readb(musb_base, MUSB_DEVCTL);
>
> for (i = 0; i < musb->config->num_eps; ++i) {
> - struct musb_hw_ep *hw_ep;
> -
> - hw_ep = &musb->endpoints[i];
> - if (!hw_ep)
> - continue;
> -
> - epio = hw_ep->regs;
> + epio = musb->endpoints[i].regs;
Why is this needed in the stable releases? It just seems to remove
unused code, but does not change any logic at all, so why backport it?
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-14 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 17:01 [PATCH 5.10 0/1] " Danila Chernetsov
2023-03-14 17:01 ` [PATCH 5.10 1/1] " Danila Chernetsov
2023-03-14 17:06 ` Sergey Shtylyov
2023-03-14 17:08 ` Greg Kroah-Hartman [this message]
[not found] ` <10af6434-a466-7884-5650-fd8de01d540b@mail.ru>
2023-03-15 4:26 ` Greg Kroah-Hartman
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=ZBCqHJz8zYeXQ3Q7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=b-liu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=listdansp@mail.ru \
--cc=lvc-project@linuxtesting.org \
--cc=s.shtylyov@omp.ru \
--cc=stable@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
all inboxes | Powered by JetHome®