From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/5] cfg80211: better station change handling
Date: Tue, 19 Feb 2013 12:08:37 +0100 [thread overview]
Message-ID: <1361272117.8553.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1360943194-14810-1-git-send-email-johannes@sipsolutions.net> (sfid-20130215_164643_028140_C8C65636)
On Fri, 2013-02-15 at 16:46 +0100, Johannes Berg wrote:
> I've now tested TDLS as well, and it just needed a few changes.
Did some more testing and applied the patches.
johannes
prev parent reply other threads:[~2013-02-19 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 15:46 [PATCH 0/5] cfg80211: better station change handling Johannes Berg
2013-02-15 15:46 ` [PATCH 1/5] cfg80211: clean up mesh plink station change API Johannes Berg
2013-02-15 15:46 ` [PATCH 2/5] cfg80211: constify station parameter pointers Johannes Berg
2013-02-15 15:46 ` [PATCH 3/5] cfg80211: clean up station WME attribute parsing Johannes Berg
2013-02-15 15:46 ` [PATCH 4/5] cfg80211: unify station WME parsing Johannes Berg
2013-02-15 15:46 ` [PATCH 5/5] cfg80211: comprehensively check station changes Johannes Berg
2013-02-15 16:05 ` [PATCH v2 " Johannes Berg
2013-02-19 11:08 ` Johannes Berg [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=1361272117.8553.2.camel@jlt4.sipsolutions.net \
--to=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).