Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: jussi.kivilinna@mbnet.fi
Cc: linux-wireless@vger.kernel.org
Subject: re: rndis_wlan: split getting current channel to separate function
Date: Wed, 29 Feb 2012 09:32:34 +0300	[thread overview]
Message-ID: <20120229063234.GB18031@elgon.mountain> (raw)

Hello Jussi,

The patch b5257c952: "rndis_wlan: workaround device not returning bss
for currently connected AP" from Nov 9, 2011, leads to the following
warning:
drivers/net/wireless/rndis_wlan.c:1374:36: warning: cast to restricted __le16
drivers/net/wireless/rndis_wlan.c:1374:36: warning: cast from restricted __le32

  1372  
  1373          if (beacon_interval)
  1374                  *beacon_interval = le16_to_cpu(config.beacon_period);
  1375          return channel;

The problem is that config.beacon_period is declared as le32 but we're
using it as le16.

regards,
dan carpenter


             reply	other threads:[~2012-02-29  6:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  6:32 Dan Carpenter [this message]
2012-02-29  8:09 ` rndis_wlan: split getting current channel to separate function Jussi Kivilinna
2012-02-29  8:47   ` 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=20120229063234.GB18031@elgon.mountain \
    --to=dan.carpenter@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox