From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: mac80211-next 2014-02-21
Date: Mon, 24 Feb 2014 15:03:58 -0500 [thread overview]
Message-ID: <20140224200358.GG24810@tuxdriver.com> (raw)
In-Reply-To: <1392976254.4346.45.camel@jlt4.sipsolutions.net>
On Fri, Feb 21, 2014 at 10:50:54AM +0100, Johannes Berg wrote:
> Hi John,
>
> More content for -next ... :) I've merged wireless-next to get the TDLS
> patch to apply properly without causing undue conflicts in mwifiex.
>
> This time, I have a number of small fixes and improvements, and those
> are fairly straight-forward. More interesting changes come from Luca
> with some preparations for the CSA work, mostly around interface/channel
> combinations checking. One other possibly interesting change is a small
> one by myself to add NAPI support back to mac80211, which can help
> improve TCP behaviour through GRO.
>
> Let me know if there's any problem!
>
> johannes
>
> ---
>
> The following changes since commit 35582ad9d342025653aaf28ed321bf5352488d7f:
>
> Staging: rtl8812ae: remove modules field of rate_control_ops (2014-02-13 15:23:23 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git for-john
>
> for you to fetch changes up to 6658ab80fd4ef940fc2366ddb66690a15ea69c18:
>
> mac80211: ibss: handle cfg80211_chandef_dfs_required() error codes (2014-02-21 09:37:46 +0100)
Pulling now...
--
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:[~2014-02-24 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 9:50 pull-request: mac80211-next 2014-02-21 Johannes Berg
2014-02-24 20:03 ` 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=20140224200358.GG24810@tuxdriver.com \
--to=linville@tuxdriver.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).