All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gioh Kim <gi-oh.kim@profitbricks.com>
To: gregkh@linuxfoundation.org, sergio.paracuellos@gmail.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	gurugio@hanmail.net, Gioh Kim <gi-oh.kim@profitbricks.com>
Subject: [PATCH 0/2] staging: wlan-ng: remove Sparse warnings for reading __le16
Date: Mon, 13 Mar 2017 14:14:24 +0100	[thread overview]
Message-ID: <1489410866-19639-1-git-send-email-gi-oh.kim@profitbricks.com> (raw)

Hi,

I found that many "warning: cast to restricted __le16" in staging/wlan-ng directory.
I don't know why but many structures has u16 type variable, not __le16.
And they are read by le16_to_cpu macro.

So I introduced a wrapper macro to read u16 type variable without Sparse warning,
and convert it into u32 type.
I hope this could help.


Gioh Kim (2):
  taging: wlan-ng: introduce a macro read_u16
  staging: wlan-ng: prism2sta.c: apply read_u16 macro

 drivers/staging/wlan-ng/prism2mgmt.h |   3 +
 drivers/staging/wlan-ng/prism2sta.c  | 128 +++++++++++++++++------------------
 2 files changed, 67 insertions(+), 64 deletions(-)

-- 
2.5.0

             reply	other threads:[~2017-03-13 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 13:14 Gioh Kim [this message]
2017-03-13 13:14 ` [PATCH 1/2] staging: wlan-ng: introduce a macro read_u16 Gioh Kim
2017-03-14  0:02   ` Greg KH
2017-03-13 13:14 ` [PATCH 2/2] staging: wlan-ng: prism2sta.c: apply read_u16 macro Gioh Kim

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=1489410866-19639-1-git-send-email-gi-oh.kim@profitbricks.com \
    --to=gi-oh.kim@profitbricks.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gurugio@hanmail.net \
    --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 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.