All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rndis_wlan: fix sparse warnings
Date: Wed, 20 Feb 2008 15:20:15 -0500	[thread overview]
Message-ID: <20080220202015.GC3825@tuxdriver.com> (raw)
In-Reply-To: <1203504466.17534.16.camel@johannes.berg>

On Wed, Feb 20, 2008 at 11:47:45AM +0100, Johannes Berg wrote:
> It is obviously wrong to use an enum in a little endian struct,
> and those other enums should be declared differently.
> 
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> ---
>  drivers/net/wireless/rndis_wlan.c |   14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> --- everything.orig/drivers/net/wireless/rndis_wlan.c	2008-02-20 11:43:22.000000000 +0100
> +++ everything/drivers/net/wireless/rndis_wlan.c	2008-02-20 11:45:35.000000000 +0100
> @@ -228,9 +228,9 @@ struct NDIS_WLAN_BSSID_EX {
>  	struct NDIS_802_11_SSID Ssid;
>  	__le32 Privacy;
>  	__le32 Rssi;
> -	enum NDIS_802_11_NETWORK_TYPE NetworkTypeInUse;
> +	__le32 NetworkTypeInUse;
>  	struct NDIS_802_11_CONFIGURATION Configuration;
> -	enum NDIS_802_11_NETWORK_INFRASTRUCTURE InfrastructureMode;
> +	__le32 InfrastructureMode;
>  	u8 SupportedRates[NDIS_802_11_LENGTH_RATES_EX];
>  	__le32 IELength;
>  	u8 IEs[0];

This suggests that the values in the enum need to be explicitly
defined, does it not?

-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2008-02-20 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 10:47 [PATCH] rndis_wlan: fix sparse warnings Johannes Berg
2008-02-20 20:20 ` John W. Linville [this message]
2008-02-21  9:29   ` Johannes Berg
2008-02-21 16:20     ` John W. Linville
2008-02-24 11:02 ` Jussi Kivilinna

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=20080220202015.GC3825@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=jussi.kivilinna@mbnet.fi \
    --cc=linux-wireless@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 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.