All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:34:18 +0300	[thread overview]
Message-ID: <1279780458.2322.25.camel@powerslave> (raw)
In-Reply-To: <1279729917-4451-1-git-send-email-linville@tuxdriver.com>

Hi John,

Great that someone finally made the endianess changes that we never had
the time to do for wl1251. Thanks for that! :)

I took a look at your patch and I have a few minor comments below, but
the best person to comment would certainly be Kalle, not me ;)


On Wed, 2010-07-21 at 18:31 +0200, ext John W. Linville wrote:
> diff --git a/drivers/net/wireless/wl12xx/wl1251_boot.c b/drivers/net/wireless/wl12xx/wl1251_boot.c
> index 2545123..c688895 100644
> --- a/drivers/net/wireless/wl12xx/wl1251_boot.c
> +++ b/drivers/net/wireless/wl12xx/wl1251_boot.c

[...]

> @@ -467,7 +467,7 @@ static int wl1251_boot_upload_nvs(struct wl1251 *wl)
>  		val = (nvs_ptr[0] | (nvs_ptr[1] << 8)
>  		       | (nvs_ptr[2] << 16) | (nvs_ptr[3] << 24));
>  
> -		val = cpu_to_le32(val);
> +		val = (u32 __force) cpu_to_le32(val);

This will work, but such casts always make me a bit suspicious.  I think
this is fine for now, but later I think we should make sure that all the
_write() functions explicitly receive __le32 as val, or receives the
cpu's u32 and converts it before actually writing the value, for clarity
reasons.  Kalle, what do you think?


> diff --git a/drivers/net/wireless/wl12xx/wl1251_tx.c b/drivers/net/wireless/wl12xx/wl1251_tx.c
> index c822318..a38ec19 100644
> --- a/drivers/net/wireless/wl12xx/wl1251_tx.c
> +++ b/drivers/net/wireless/wl12xx/wl1251_tx.c

[...]

> @@ -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));

Maybe some casts are needed too, I didn't check that, but regarding the
endianess, I think this is how it should go.  It's the same thing as the
length parameter:

> +		length = le16_to_cpu(tx_hdr->length) + WL1251_TKIP_IV_SPACE;
> +		tx_hdr->length = cpu_to_le16(length);

...which is treated correctly here.



-- 
Cheers,
Luca.


  reply	other threads:[~2010-07-22  6:41 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 [this message]
2010-07-22  7:38   ` Luciano Coelho
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=1279780458.2322.25.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.