From: Michael Buesch <mb@bu3sch.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Jiri Benc <jbenc@suse.cz>,
"John Linville" <linville@tuxdriver.com>,
Michael Wu <flamingice@sourmilk.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/3] d80211-bcm43xx: Add control structure for beacontemplates
Date: Sat, 3 Feb 2007 17:47:59 +0100 [thread overview]
Message-ID: <200702031747.59783.mb@bu3sch.de> (raw)
In-Reply-To: <200702031725.21428.IvDoorn@gmail.com>
On Saturday 03 February 2007 17:25, Ivo van Doorn wrote:
> Drivers that require beacon templates will also have the
> control structure at their disposal and should always free it.
>
> bcm43xx doesn't use the control structure, but should still free it.
>
> Signed-off-by Ivo van Doorn <IvDoorn@gmail.com>
>
> ---
>
> diff --git a/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c b/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
> index 9f4d51d..24be8f5 100644
> --- a/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
> +++ b/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
> @@ -2732,8 +2732,10 @@ static int bcm43xx_config_interface(struct ieee80211_hw *hw,
> if (bcm43xx_is_mode(wl, IEEE80211_IF_TYPE_AP)) {
> assert(conf->type == IEEE80211_IF_TYPE_AP);
> bcm43xx_set_ssid(dev, conf->ssid, conf->ssid_len);
> - if (conf->beacon)
> + if (conf->beacon) {
> bcm43xx_refresh_templates(dev, conf->beacon);
> + kfree(conf->beacon_control);
> + }
> }
> }
ACK to this patch, for now.
I will take care to actually properly set the beacon tx control
parameters in hardware (the possible ones) with a later patch.
--
Greetings Michael.
prev parent reply other threads:[~2007-02-03 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 16:25 [PATCH 2/3] d80211-bcm43xx: Add control structure for beacontemplates Ivo van Doorn
2007-02-03 16:47 ` Michael Buesch [this message]
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=200702031747.59783.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=flamingice@sourmilk.net \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@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).