From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xhci: remove unused variable
Date: Wed, 21 Apr 2021 18:39:48 +0800 [thread overview]
Message-ID: <1bf6144c-9385-d7ff-a30c-f0bb17f9c2e6@linux.alibaba.com> (raw)
In-Reply-To: <YGWj9KKtEd+sAdtH@kroah.com>
On 2021/4/1 18:44, Greg KH wrote:
> On Thu, Apr 01, 2021 at 06:17:15PM +0800, Jiapeng Chong wrote:
>> Fix the following clang warning:
>>
>> drivers/usb/host/xhci.c:1346:15: warning: variable ‘len’ set but not
>> used [-Wunused-but-set-variable].
>>
>> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
>> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
>> ---
>> drivers/usb/host/xhci.c | 8 +++-----
>> 1 file changed, 3 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
>> index 1975016..0ead09c 100644
>> --- a/drivers/usb/host/xhci.c
>> +++ b/drivers/usb/host/xhci.c
>> @@ -1343,7 +1343,6 @@ static bool xhci_urb_temp_buffer_required(struct usb_hcd *hcd,
>>
>> static void xhci_unmap_temp_buf(struct usb_hcd *hcd, struct urb *urb)
>> {
>> - unsigned int len;
>> unsigned int buf_len;
>> enum dma_data_direction dir;
>>
>> @@ -1359,10 +1358,9 @@ static void xhci_unmap_temp_buf(struct usb_hcd *hcd, struct urb *urb)
>> dir);
>>
>> if (usb_urb_dir_in(urb))
>> - len = sg_pcopy_from_buffer(urb->sg, urb->num_sgs,
>> - urb->transfer_buffer,
>> - buf_len,
>> - 0);
>> + sg_pcopy_from_buffer(urb->sg, urb->num_sgs,
>> + urb->transfer_buffer,
>> + buf_len, 0);
>>
>> urb->transfer_flags &= ~URB_DMA_MAP_SINGLE;
>> kfree(urb->transfer_buffer);
>> --
>> 1.8.3.1
>>
>
> Why resubmit this same change when I rejected it in the past?
>
> {sigh}
>
> greg k-h
>
Thanks for reminding us. We'll pay more attention next time.
prev parent reply other threads:[~2021-04-21 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 10:17 Jiapeng Chong
2021-04-01 10:44 ` Greg KH
2021-04-21 10:39 ` Jiapeng Chong [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=1bf6144c-9385-d7ff-a30c-f0bb17f9c2e6@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.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
all inboxes | Powered by JetHome®