From: Yuri Ershov <ext-yuri.ershov@nokia.com>
To: johannes@sipsolutions.net
Cc: ext-yuri.kululin@nokia.com, linux-wireless@vger.kernel.org
Subject: [RFC 0/3] Update for some defects
Date: Tue, 29 Jun 2010 15:08:05 +0400 [thread overview]
Message-ID: <cover.1277808543.git.ext-yuri.ershov@nokia.com> (raw)
Hello,
These are some proposals for wireless code minor defects.
Yuri Ershov (3):
mac80211: Put some code under MESH macro
nl80211: Fix memory leaks
cfg80211: Update of regulatory request initiator handling
net/mac80211/tx.c | 2 ++
net/wireless/nl80211.c | 2 ++
net/wireless/reg.c | 3 ++-
3 files changed, 6 insertions(+), 1 deletions(-)
next reply other threads:[~2010-06-29 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 11:08 Yuri Ershov [this message]
2010-06-29 11:08 ` [RFC 1/3] mac80211: Put some code under MESH macro Yuri Ershov
2010-06-29 11:08 ` [RFC 2/3] nl80211: Fix memory leaks Yuri Ershov
2010-06-29 11:08 ` [RFC 3/3] cfg80211: Update of regulatory request initiator handling Yuri Ershov
2010-06-29 13:48 ` [RFC 0/3] Update for some defects John W. Linville
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=cover.1277808543.git.ext-yuri.ershov@nokia.com \
--to=ext-yuri.ershov@nokia.com \
--cc=ext-yuri.kululin@nokia.com \
--cc=johannes@sipsolutions.net \
--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).