From: Luciano Coelho <luciano.coelho@nokia.com>
To: "ext John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Kalle Valo <kalle.valo@iki.fi>
Subject: Re: [PATCH] wl1251: fix sparse-generated warnings
Date: Thu, 22 Jul 2010 10:38:47 +0300 [thread overview]
Message-ID: <1279784327.2322.33.camel@powerslave> (raw)
In-Reply-To: <1279780458.2322.25.camel@powerslave>
On Thu, 2010-07-22 at 08:34 +0200, Coelho Luciano (Nokia-MS/Helsinki)
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? Wouldn't the following be the right thing to
> do then?
>
> fc = cpu_to_le16(le16_to_cpu(skb->data) + sizeof(*tx_hdr));
Ugh, as Johannes pointed out, what I said here is completely non-sense.
Please ignore this before-my-morning-coffee lapse. ;)
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-07-22 7:39 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 [this message]
2010-07-22 7:45 ` Kalle Valo
2010-07-22 7:57 ` Luciano Coelho
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=1279784327.2322.33.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 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.