From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linville@tuxdriver.com, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [PATCH 0/4] cfg80211: few minor enhancements based on reg requests
Date: Sat, 21 Feb 2009 00:24:12 -0500 [thread overview]
Message-ID: <1235193856-3524-1-git-send-email-lrodriguez@atheros.com> (raw)
These are a few cleanups based on the new strategy to use regutory requests
structures from the workqueue. We still pass the wiphy directly to
__regulatory_hint() and ignore_request() as its used often.
Luis R. Rodriguez (4):
cfg80211: make __regulatory_hint() static
cfg80211: pass the regulatory_request struct in __regulatory_hint()
cfg80211: do not kzalloc() again for a new request on
__regulatory_hint
cfg80211: pass the regulatory_request to ignore_request
net/wireless/reg.c | 106 ++++++++++++++++++++++-----------------------------
net/wireless/reg.h | 23 -----------
2 files changed, 46 insertions(+), 83 deletions(-)
next reply other threads:[~2009-02-21 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 5:24 Luis R. Rodriguez [this message]
2009-02-21 5:24 ` [PATCH 1/4] cfg80211: make __regulatory_hint() static Luis R. Rodriguez
2009-02-21 5:24 ` [PATCH 2/4] cfg80211: pass the regulatory_request struct in __regulatory_hint() Luis R. Rodriguez
2009-02-21 5:24 ` [PATCH 3/4] cfg80211: do not kzalloc() again for a new request on __regulatory_hint Luis R. Rodriguez
2009-02-21 5:24 ` [PATCH 4/4] cfg80211: pass the regulatory_request to ignore_request Luis R. Rodriguez
2009-02-24 2:00 ` [PATCH 0/4] cfg80211: few minor enhancements based on reg requests Johannes Berg
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=1235193856-3524-1-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox