From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: mac80211-next 2014-06-24
Date: Tue, 24 Jun 2014 19:07:58 +0200 [thread overview]
Message-ID: <1403629678.10831.14.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1403626964.10831.12.camel@jlt4.sipsolutions.net> (sfid-20140624_182313_006352_507DF583)
On Tue, 2014-06-24 at 18:22 +0200, Johannes Berg wrote:
> The biggest thing here is probably Arik's TDLS rework, beyond that we
> have smaller improvements and features like David's scanning IE thing,
The latter seems to cause some issues with the ath9k multi-channel code,
I didn't realize you'd merged that in.
The fix is not very difficult, so maybe you can just fix it when you
merge? See commit eb6a61549f530f1cc435512df3799f656094ba83 for how all
the other drivers were changed.
johannes
next prev parent reply other threads:[~2014-06-24 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 16:22 pull-request: mac80211-next 2014-06-24 Johannes Berg
2014-06-24 17:07 ` Johannes Berg [this message]
2014-06-25 19:18 ` John W. Linville
2014-06-25 19:28 ` John W. Linville
2014-06-25 19:18 ` 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=1403629678.10831.14.camel@jlt4.sipsolutions.net \
--to=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;
as well as URLs for NNTP newsgroup(s).