From: Guillaume Brogi <gui-gui@netcourrier.com>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: Bhumika Goyal <bhumirks@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192u: Convert __le16 to cpu before casting to u32
Date: Sat, 8 Apr 2017 20:32:36 +0200 [thread overview]
Message-ID: <20170408183236.2zgiedzu3jjffdb5@nexon> (raw)
In-Reply-To: <20170408103125.GA19569@kroah.com>
On Sat, Apr 08, 2017 at 12:31:25PM +0200, Greg Kroah-Hartman wrote:
> On Sun, Mar 26, 2017 at 12:24:14AM +0100, Guillaume Brogi wrote:
> >
> > This patch fixes the following sparse warnings:
> > drivers/staging/rtl8192u/r8192U_dm.c:2307:49: warning: cast from restricted __le16
> > drivers/staging/rtl8192u/r8192U_dm.c:2308:44: warning: cast from restricted __le16
> > drivers/staging/rtl8192u/r8192U_dm.c:2309:44: warning: cast from restricted __le16
> >
> > Those three members of qos_parameters are indeed __le16 so they should
> > be converted to the cpu's endianness before being cast to u32.
> >
> > The lines are over the 80 character limit. They already were, and, for
> > the sake of readability, I don't think they should be split.
>
> Please fix up your subject: line to match other patches for this driver,
> I almost missed it :(
>
Sorry about that. I realised my mistake after sending the email.
> >
> > Signed-off-by: Guillaume Brogi <gui-gui@netcourrier.com>
> > ---
> > drivers/staging/rtl8192u/r8192U_dm.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c
> > index 9209aad0515e..5946c1f8d37d 100644
> > --- a/drivers/staging/rtl8192u/r8192U_dm.c
> > +++ b/drivers/staging/rtl8192u/r8192U_dm.c
> > @@ -2304,9 +2304,9 @@ static void dm_check_edca_turbo(
> > /* For Each time updating EDCA parameter, reset EDCA turbo mode status. */
> > dm_init_edca_turbo(dev);
> > u1bAIFS = qos_parameters->aifs[0] * ((mode&(IEEE_G|IEEE_N_24G)) ? 9 : 20) + aSifsTime;
> > - u4bAcParam = (((u32)(qos_parameters->tx_op_limit[0])) << AC_PARAM_TXOP_LIMIT_OFFSET)|
> > - (((u32)(qos_parameters->cw_max[0])) << AC_PARAM_ECW_MAX_OFFSET)|
> > - (((u32)(qos_parameters->cw_min[0])) << AC_PARAM_ECW_MIN_OFFSET)|
> > + u4bAcParam = (((u32)le16_to_cpu(qos_parameters->tx_op_limit[0])) << AC_PARAM_TXOP_LIMIT_OFFSET) |
> > + (((u32)le16_to_cpu(qos_parameters->cw_max[0])) << AC_PARAM_ECW_MAX_OFFSET) |
> > + (((u32)le16_to_cpu(qos_parameters->cw_min[0])) << AC_PARAM_ECW_MIN_OFFSET) |
> > ((u32)u1bAIFS << AC_PARAM_AIFS_OFFSET);
> > /*write_nic_dword(dev, WDCAPARA_ADD[i], u4bAcParam);*/
> > write_nic_dword(dev, EDCAPARA_BE, u4bAcParam);
>
> How are you sure that this change is correct? How did you verify it?
>
Sadly, I don't have the hardware to test that. I only checked the code
and compiled it.
> thanks,
>
Cheers,
--
Guillaume Brogi
next prev parent reply other threads:[~2017-04-08 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 23:24 [PATCH] " Guillaume Brogi
2017-04-08 10:31 ` Greg Kroah-Hartman
2017-04-08 18:32 ` Guillaume Brogi [this message]
2017-05-07 12:56 ` [PATCH] staging: rtl8192u: " Guillaume Brogi
2017-05-12 8:08 ` Greg Kroah-Hartman
2017-05-12 20:09 ` Guillaume Brogi
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=20170408183236.2zgiedzu3jjffdb5@nexon \
--to=gui-gui@netcourrier.com \
--cc=bhumirks@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--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 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®