From: Perry Hooker <perry.hooker@gmail.com>
To: gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Perry Hooker <perry.hooker@gmail.com>
Subject: [PATCH] staging: r8712u: remove unnecessary le32_to_cpu
Date: Thu, 9 Feb 2017 20:51:55 -0700 [thread overview]
Message-ID: <1486698715-81145-1-git-send-email-perry.hooker@gmail.com> (raw)
This patch fixes the following sparse warning:
drivers/staging/rtl8712/usb_ops_linux.c:212:33: warning: cast to restricted __le32
Signed-off-by: Perry Hooker <perry.hooker@gmail.com>
---
drivers/staging/rtl8712/usb_ops_linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8712/usb_ops_linux.c b/drivers/staging/rtl8712/usb_ops_linux.c
index fc6bb0b..259ef8f 100644
--- a/drivers/staging/rtl8712/usb_ops_linux.c
+++ b/drivers/staging/rtl8712/usb_ops_linux.c
@@ -209,7 +209,7 @@ static void r8712_usb_read_port_complete(struct urb *purb)
precvbuf->transfer_len = purb->actual_length;
pbuf = (uint *)precvbuf->pbuf;
- isevt = le32_to_cpu(*(pbuf + 1)) & 0x1ff;
+ isevt = *(pbuf + 1) & 0x1ff;
if ((isevt & 0x1ff) == 0x1ff) {
r8712_rxcmd_event_hdl(padapter, pbuf);
skb_queue_tail(&precvpriv->rx_skb_queue, pskb);
--
2.4.11
next reply other threads:[~2017-02-10 4:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 3:51 Perry Hooker [this message]
2017-02-10 14:08 ` [PATCH] staging: r8712u: remove unnecessary le32_to_cpu Greg KH
2017-02-10 14:52 ` Larry Finger
2017-02-10 14:58 ` Greg KH
2017-02-10 15:07 ` Larry Finger
2017-02-10 18:24 ` Perry Hooker
2017-02-10 18:23 ` [PATCH] staging: r8712u: use __le32 type for little-endian data Perry Hooker
2017-02-10 20:55 ` Larry Finger
2017-02-11 19:04 ` Perry Hooker
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=1486698715-81145-1-git-send-email-perry.hooker@gmail.com \
--to=perry.hooker@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.