linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Kalle Valo <kalle.valo@iki.fi>
Cc: "ext John W. Linville" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wl1251: fix sparse-generated warnings
Date: Thu, 22 Jul 2010 10:57:23 +0300	[thread overview]
Message-ID: <1279785443.2322.37.camel@powerslave> (raw)
In-Reply-To: <4C47F706.4060102@iki.fi>

On Thu, 2010-07-22 at 09:45 +0200, ext Kalle Valo wrote:
> On 07/22/2010 08:34 AM, Luciano Coelho wrote:
> >> @@ -191,11 +191,13 @@ static int wl1251_tx_send_packet(struct wl1251 *wl, struct sk_buff *skb,
> >>  	if (control->control.hw_key &&
> >>  	    control->control.hw_key->alg == ALG_TKIP) {
> >>  		int hdrlen;
> >> -		u16 fc;
> >> +		__le16 fc;
> >> +		u16 length;
> >>  		u8 *pos;
> >>  
> >> -		fc = *(u16 *)(skb->data + sizeof(*tx_hdr));
> >> -		tx_hdr->length += WL1251_TKIP_IV_SPACE;
> >> +		fc = *(__le16 *)(skb->data + sizeof(*tx_hdr));
> > 
> > Is this going to work? sizeof(*tx_hdr), and the operation, will be in
> > the cpu's endianess, right?
> 
> I think this is correct. We first calculate a pointer to a __le16 value
> and then dereference that value to a __le16 variable.

Yes, you're right, I got totally confused for some reason, as I already
pointed out on my other email.  I completely missed the fact that we
were dealing with pointers here.  It seems like my brain works as that
of a Java programmer before my morning dose of caffeine :P

-- 
Cheers,
Luca.


  reply	other threads:[~2010-07-22  8:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 16:31 [PATCH] wl1251: fix sparse-generated warnings John W. Linville
2010-07-22  6:34 ` Luciano Coelho
2010-07-22  7:38   ` Luciano Coelho
2010-07-22  7:45   ` Kalle Valo
2010-07-22  7:57     ` Luciano Coelho [this message]
2010-07-22 12:04     ` Bob Copeland
2010-07-22 13:16       ` John W. Linville
2010-07-22 13:21     ` John W. Linville
2010-07-23  8:14       ` Kalle Valo
2010-07-22  8:45 ` Kalle Valo
2010-07-22  8:52   ` Luciano Coelho
2010-07-22  9:21     ` Kalle Valo

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=1279785443.2322.37.camel@powerslave \
    --to=luciano.coelho@nokia.com \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).