From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: min.guo@mediatek.com, Bin Liu <b-liu@ti.com>,
Alan Stern <stern@rowland.harvard.edu>,
Matthias Brugger <matthias.bgg@gmail.com>,
chunfeng.yun@mediatek.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3] usb: musb: remove unused variable 'devctl'
Date: Thu, 10 Dec 2020 20:33:30 +0300 [thread overview]
Message-ID: <e59a754b-ad3e-2f8f-417a-96ddfcd3cbd3@gmail.com> (raw)
In-Reply-To: <X9I4L3E9EJlcPMEu@kroah.com>
On 12/10/20 6:01 PM, Greg Kroah-Hartman wrote:
[...]
>>> From: Min Guo <min.guo@mediatek.com>
>>>
>>> Remove unused 'devctl' variable to fix compile warnings:
>>>
>>> drivers/usb/musb/musbhsdma.c: In function 'dma_controller_irq':
>>> drivers/usb/musb/musbhsdma.c:324:8: warning: variable 'devctl' set
>>> but not used [-Wunused-but-set-variable]
>>>
>>> Signed-off-by: Min Guo <min.guo@mediatek.com>
>>> ---
>>> changes in v3
>>> suggested by Greg Kroah-Hartman:
>>> Add a comment.
>>>
>>> changes in v2
>>> suggested by Alan Stern:
>>> Add void before musb_read to indicate that the register MUSB_DEVCTL
>>> was intended to be read and discarded.
>>> ---
>>> drivers/usb/musb/musbhsdma.c | 8 +++++---
>>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/usb/musb/musbhsdma.c b/drivers/usb/musb/musbhsdma.c
>>> index 0aacfc8be5a1..2a345b4ad015 100644
>>> --- a/drivers/usb/musb/musbhsdma.c
>>> +++ b/drivers/usb/musb/musbhsdma.c
>> [...]
>>> @@ -336,7 +334,11 @@ irqreturn_t dma_controller_irq(int irq, void *private_data)
>>> < musb_channel->len) ?
>>> "=> reconfig 0" : "=> complete");
>>> - devctl = musb_readb(mbase, MUSB_DEVCTL);
>>> + /*
>>> + * Some hardware may need to read the
>>> + * MUSB_DEVCTL register once to take effect.
>>> + */
>>> + (void)musb_readb(mbase, MUSB_DEVCTL);
>>
>> Hm, forcibly reading DevCtl in the DMA driver... sounds quite
>> nonsensically. Lemme take a look...
>
> What happened to your look?
I thought I posted it the same day... Indeed, here it is, archived:
https://marc.info/?l=linux-usb&m=160621841910477
> thanks,
>
> greg k-h
MBR, Sergei
prev parent reply other threads:[~2020-12-10 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 8:49 [PATCH v3] usb: musb: remove unused variable 'devctl' min.guo
2020-11-24 9:13 ` Sergei Shtylyov
2020-11-24 11:45 ` Sergei Shtylyov
2020-12-10 15:01 ` Greg Kroah-Hartman
2020-12-10 17:33 ` Sergei Shtylyov [this message]
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=e59a754b-ad3e-2f8f-417a-96ddfcd3cbd3@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=b-liu@ti.com \
--cc=chunfeng.yun@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=min.guo@mediatek.com \
--cc=stern@rowland.harvard.edu \
/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).