From: Maciek Borzecki <maciek.borzecki@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Maciek Borzecki <maciek.borzecki@gmail.com>
Subject: [PATCH] staging wlan-ng: mark PDA buf as __le16
Date: Fri, 7 Apr 2017 14:47:55 +0200 [thread overview]
Message-ID: <4c87e137d9390a0f4e4b4f5aeb264569fc1e57d9.1491568884.git.maciek.borzecki@gmail.com> (raw)
PDA buffer contains little-endian data, clearly mark it as such.
Fixes sparse warnings:
drivers/staging/wlan-ng/hfa384x_usb.c:2359:34: warning: cast to restricted __le16
drivers/staging/wlan-ng/hfa384x_usb.c:2360:35: warning: cast to restricted __le16
drivers/staging/wlan-ng/hfa384x_usb.c:2382:44: warning: cast to restricted __le16
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
---
drivers/staging/wlan-ng/hfa384x_usb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c b/drivers/staging/wlan-ng/hfa384x_usb.c
index 6134eba5cad4693997faf8d2d77947ff7e8b0713..64848778834cae1d341c59ecce756d11b218b4c8 100644
--- a/drivers/staging/wlan-ng/hfa384x_usb.c
+++ b/drivers/staging/wlan-ng/hfa384x_usb.c
@@ -2316,7 +2316,7 @@ int hfa384x_drvr_ramdl_write(struct hfa384x *hw, u32 daddr, void *buf, u32 len)
int hfa384x_drvr_readpda(struct hfa384x *hw, void *buf, unsigned int len)
{
int result = 0;
- u16 *pda = buf;
+ __le16 *pda = buf;
int pdaok = 0;
int morepdrs = 1;
int currpdr = 0; /* word offset of the current pdr */
--
2.9.3
next reply other threads:[~2017-04-07 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 12:47 Maciek Borzecki [this message]
2017-04-08 11:01 ` Greg Kroah-Hartman
2017-04-08 13:18 ` Maciek Borzecki
2017-04-08 13:22 ` Maciek Borzecki
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=4c87e137d9390a0f4e4b4f5aeb264569fc1e57d9.1491568884.git.maciek.borzecki@gmail.com \
--to=maciek.borzecki@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergio.paracuellos@gmail.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
all inboxes | Powered by JetHome®