From: simran singhal <singhalsimran0@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sergio.paracuellos@gmail.com, juliana.orod@gmail.com,
thomas.petazzoni@free-electrons.com, noralf@tronnes.org,
outreachy-kernel@googlegroups.com
Subject: [PATCH 2/6] staging: wlan-ng: Fix sparse warnings
Date: Thu, 2 Mar 2017 15:19:02 +0530 [thread overview]
Message-ID: <1488448146-29452-2-git-send-email-singhalsimran0@gmail.com> (raw)
In-Reply-To: <1488448146-29452-1-git-send-email-singhalsimran0@gmail.com>
This patch fixes the following sparse warnings:
drivers/staging/wlan-ng/hfa384x_usb.c:1327:34: warning: incorrect type in assignment (different base types)
drivers/staging/wlan-ng/hfa384x_usb.c:1327:34: expected unsigned short [unsigned] [usertype] type
drivers/staging/wlan-ng/hfa384x_usb.c:1327:34: got restricted __le16 [usertype] <noident>
drivers/staging/wlan-ng/hfa384x_usb.c:1328:33: warning: incorrect type in assignment (different base types)
drivers/staging/wlan-ng/hfa384x_usb.c:1328:33: expected unsigned short [unsigned] [usertype] cmd
drivers/staging/wlan-ng/hfa384x_usb.c:1328:33: got restricted __le16 [usertype] <noident>
drivers/staging/wlan-ng/hfa384x_usb.c:1329:35: warning: incorrect type in assignment (different base types)
drivers/staging/wlan-ng/hfa384x_usb.c:1329:35: expected unsigned short [unsigned] [usertype] parm0
drivers/staging/wlan-ng/hfa384x_usb.c:1329:35: got restricted __le16 [usertype] <noident>
drivers/staging/wlan-ng/hfa384x_usb.c:1330:35: warning: incorrect type in assignment (different base types)
drivers/staging/wlan-ng/hfa384x_usb.c:1330:35: expected unsigned short [unsigned] [usertype] parm1
drivers/staging/wlan-ng/hfa384x_usb.c:1330:35: got restricted __le16 [usertype] <noident>
drivers/staging/wlan-ng/hfa384x_usb.c:1331:35: warning: incorrect type in assignment (different base types)
drivers/staging/wlan-ng/hfa384x_usb.c:1331:35: expected unsigned short [unsigned] [usertype] parm2
drivers/staging/wlan-ng/hfa384x_usb.c:1331:35: got restricted __le16 [usertype] <noident>
Signed-off-by: simran singhal <singhalsimran0@gmail.com>
---
drivers/staging/wlan-ng/hfa384x_usb.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c b/drivers/staging/wlan-ng/hfa384x_usb.c
index 6134eba..a7ff572 100644
--- a/drivers/staging/wlan-ng/hfa384x_usb.c
+++ b/drivers/staging/wlan-ng/hfa384x_usb.c
@@ -1324,11 +1324,11 @@ hfa384x_docmd(struct hfa384x *hw,
}
/* Initialize the command */
- ctlx->outbuf.cmdreq.type = cpu_to_le16(HFA384x_USB_CMDREQ);
- ctlx->outbuf.cmdreq.cmd = cpu_to_le16(cmd->cmd);
- ctlx->outbuf.cmdreq.parm0 = cpu_to_le16(cmd->parm0);
- ctlx->outbuf.cmdreq.parm1 = cpu_to_le16(cmd->parm1);
- ctlx->outbuf.cmdreq.parm2 = cpu_to_le16(cmd->parm2);
+ ctlx->outbuf.cmdreq.type = HFA384x_USB_CMDREQ;
+ ctlx->outbuf.cmdreq.cmd = cmd->cmd;
+ ctlx->outbuf.cmdreq.parm0 = cmd->parm0;
+ ctlx->outbuf.cmdreq.parm1 = cmd->parm1;
+ ctlx->outbuf.cmdreq.parm2 = cmd->parm2;
ctlx->outbufsize = sizeof(ctlx->outbuf.cmdreq);
--
2.7.4
next prev parent reply other threads:[~2017-03-02 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 9:49 [PATCH 1/6] staging: wlan-ng: Fix sparse warning of restricted __le16 simran singhal
2017-03-02 9:48 ` [Outreachy kernel] " Julia Lawall
2017-03-02 9:50 ` Julia Lawall
2017-03-02 11:11 ` SIMRAN SINGHAL
2017-03-02 11:14 ` Julia Lawall
2017-03-02 17:34 ` Alison Schofield
2017-03-02 9:49 ` simran singhal [this message]
2017-03-02 9:49 ` [PATCH 3/6] staging: wlan-ng: Fix sparse warnings in hfa384x_usb.c simran singhal
2017-03-02 9:49 ` [PATCH 4/6] staging: fbtft: Fix sparse warnings of incorrect type in assignment simran singhal
2017-03-02 9:49 ` [PATCH 5/6] staging: rtl8192u: Fix Sparse warning of cast from restricted __le16 simran singhal
2017-03-02 9:49 ` [PATCH 6/6] staging: rtl8192u: Fix Sparse warning of cast to " simran singhal
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=1488448146-29452-2-git-send-email-singhalsimran0@gmail.com \
--to=singhalsimran0@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=juliana.orod@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sergio.paracuellos@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
/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