From: "John W. Linville" <linville@tuxdriver.com>
To: Yuri Ershov <ext-yuri.ershov@nokia.com>
Cc: johannes@sipsolutions.net, ext-yuri.kululin@nokia.com,
linux-wireless@vger.kernel.org
Subject: Re: [RFC 0/3] Update for some defects
Date: Tue, 29 Jun 2010 09:48:29 -0400 [thread overview]
Message-ID: <20100629134829.GB5296@tuxdriver.com> (raw)
In-Reply-To: <cover.1277808543.git.ext-yuri.ershov@nokia.com>
On Tue, Jun 29, 2010 at 03:08:05PM +0400, Yuri Ershov wrote:
> Yuri Ershov (3):
> mac80211: Put some code under MESH macro
> nl80211: Fix memory leaks
> cfg80211: Update of regulatory request initiator handling
These all seem fine to me.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-06-29 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 11:08 [RFC 0/3] Update for some defects Yuri Ershov
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 ` John W. Linville [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=20100629134829.GB5296@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=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).