From: Gaston Gonzalez <gascoar@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: cristina.opriceana@gmail.com, hamohammed.sa@gmail.com,
gdonald@gmail.com, mahfouz.saif.elyazal@gmail.com,
paul.gortmaker@windriver.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192u: ieee80211: Fix sparse endianness warnings
Date: Sun, 31 May 2015 12:29:07 -0300 [thread overview]
Message-ID: <20150531152907.GA20006@debianG> (raw)
In-Reply-To: <20150531014527.GA8396@kroah.com>
On Sun, May 31, 2015 at 10:45:27AM +0900, Greg KH wrote:
> On Tue, May 26, 2015 at 06:47:14PM -0300, Gaston Gonzalez wrote:
> > Fix the following sparse warnings:
> >
> > drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c:663:32: warning: incorrect type in assignment (different base types)
> > drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c:663:32: expected restricted __le16 [usertype] frame_ctl
> > drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c:663:32: got int
> > drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c:664:50: warning: invalid assignment: |=
> > drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c:664:50: left side has type restricted __le16
> > drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c:664:50: right side has type int
> >
> >
> > Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
> > ---
> > drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > index d2e8b12..0477ba1 100644
> > --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
> > @@ -660,2 +660,2 @@ inline struct sk_buff *ieee80211_authentication_req(struct ieee80211_network *be
> > auth = (struct ieee80211_authentication *)
> > skb_put(skb, sizeof(struct ieee80211_authentication));
> >
> > - auth->header.frame_ctl = IEEE80211_STYPE_AUTH;
> > - if (challengelen) auth->header.frame_ctl |= IEEE80211_FCTL_WEP;
> > + auth->header.frame_ctl = cpu_to_le16(IEEE80211_STYPE_AUTH);
> > + if (challengelen)
> > + auth->header.frame_ctl |= cpu_to_le16(IEEE80211_FCTL_WEP);
> >
> > auth->header.duration_id = 0x013a; //FIXME
> >
>
> This patch doesn't apply properly for some reason, can you fix it up and
> resend?
>
> thanks,
>
> greg k-h
Hi Greg,
I couldn't find the problem with this patch. Just in case I redo the patch
against the updated staging-testing and resent it. To test it I did:
- run checkpatch
- git apply --check
- email it to myself and then 'git am' from mutt
- git log
I've just sent the patch. Please let me know if I missed something.
Thanks,
Gaston
prev parent reply other threads:[~2015-05-31 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 21:47 [PATCH] staging: rtl8192u: ieee80211: Fix sparse endianness warnings Gaston Gonzalez
2015-05-31 1:45 ` Greg KH
2015-05-31 15:29 ` Gaston Gonzalez [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=20150531152907.GA20006@debianG \
--to=gascoar@gmail.com \
--cc=cristina.opriceana@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gdonald@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mahfouz.saif.elyazal@gmail.com \
--cc=paul.gortmaker@windriver.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