linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karl Relton <karllinuxtest.relton@ntlworld.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: [PATCH] staging/wlan-ng: Explicitly set some fields in cfg80211 interface
Date: Wed, 11 Aug 2010 18:16:08 +0100	[thread overview]
Message-ID: <1281546968.2010.5.camel@dellpc> (raw)

Greg

Now that the wlan-ng driver has been switched to cfg80211 in mainline,
can this small patch be forwarded also, to catch up with some new fields
that have gone into the cfg80211 api also in this cycle.

Thanks
Karl





Explicitly set some fields in cfg80211 interface

Signed-off-by: Karl Relton <karllinuxtest.relton@ntlworld.com>

---

The cfg80211 api has introduced a few new fields. Rather than assume
what cfg80211 api does by default, set these explicitly.


--- a/drivers/staging/wlan-ng/cfg80211.c	2010-08-11 18:04:27.000000000
+0100
+++ b/drivers/staging/wlan-ng/cfg80211.c	2010-07-07 10:17:27.000000000
+0100
@@ -214,6 +214,7 @@ int prism2_get_key(struct wiphy *wiphy, 
 	} else return -ENOENT;
 	params.key_len = len;
 	params.key = wlandev->wep_keys[key_index];
+	params.seq_len = 0;
 
 	callback(cookie, &params);
 	return 0;
@@ -709,6 +710,8 @@ struct wiphy *wlan_create_wiphy(struct d
 	priv->band.n_channels = ARRAY_SIZE(prism2_channels);
 	priv->band.bitrates = priv->rates;
 	priv->band.n_bitrates = ARRAY_SIZE(prism2_rates);
+	priv->band.band = IEEE80211_BAND_2GHZ;
+	priv->band.ht_cap.ht_supported = false;
 	wiphy->bands[IEEE80211_BAND_2GHZ] = &priv->band;
 
 	set_wiphy_dev(wiphy, dev);



                 reply	other threads:[~2010-08-11 17:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1281546968.2010.5.camel@dellpc \
    --to=karllinuxtest.relton@ntlworld.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).