From: Dan Carpenter <dan.carpenter@oracle.com>
To: Arno Tiemersma <arno.tiemersma@gmail.com>
Cc: gregkh@linuxfoundation.org, mateusz.kulikowski@gmail.com,
behanw@converseincode.com, mdcasey@chabloom.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8192e: Change cpu_to_le16 to le16_to_cpu
Date: Sun, 10 May 2015 01:13:12 +0300 [thread overview]
Message-ID: <20150509221312.GF14154@mwanda> (raw)
In-Reply-To: <1431203236-5895-1-git-send-email-arno.tiemersma@gmail.com>
On Sat, May 09, 2015 at 10:27:16PM +0200, Arno Tiemersma wrote:
> Since the function auth_parse returns a u16, and
> struct rtllib_authentication.status is defined as an __le16, it seems
> that
>
> return cpu_to_le16(a->status);
>
> should be
>
> return le16_to_cpu(a->status);
>
> This change silences the following sparse warnings:
> drivers/staging/rtl8192e/rtllib_softmac.c:1817:16:
> warning: cast from restricted __le16
> drivers/staging/rtl8192e/rtllib_softmac.c:1817:16:
> warning: incorrect type in return expression (different base types)
> drivers/staging/rtl8192e/rtllib_softmac.c:1817:16:
> expected unsigned short
> drivers/staging/rtl8192e/rtllib_softmac.c:1817:16:
> got restricted __le16 [usertype] <noident>
>
> Signed-off-by: Arno Tiemersma <arno.tiemersma@gmail.com>
Your patch seems reasonable. The caller only cares about zero non-zero.
It feels like there are a bunch of endian bugs which Sparse misses in
this file. For example, ->frame_ctl is endian but it's never converted
and it's compared against cpu endian in the switch statements. (I
haven't double checked. Do your own homework before sending patches).
regards,
dan carpenter
prev parent reply other threads:[~2015-05-09 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 20:27 [PATCH v2] staging: rtl8192e: Change cpu_to_le16 to le16_to_cpu Arno Tiemersma
2015-05-09 22:13 ` Dan Carpenter [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=20150509221312.GF14154@mwanda \
--to=dan.carpenter@oracle.com \
--cc=arno.tiemersma@gmail.com \
--cc=behanw@converseincode.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mateusz.kulikowski@gmail.com \
--cc=mdcasey@chabloom.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