From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211-next 2013-06-24
Date: Mon, 24 Jun 2013 14:45:21 -0400 [thread overview]
Message-ID: <20130624184520.GD1997@tuxdriver.com> (raw)
In-Reply-To: <1372094678.8439.24.camel@jlt4.sipsolutions.net>
On Mon, Jun 24, 2013 at 07:24:38PM +0200, Johannes Berg wrote:
> John,
>
> As can be expected, I've accumulated a bunch more patches. Much of it is
> already trending towards fixes rather than new features, but some of
> those are there as well. I've removed the diffstat because git got
> confused about it, presumably because I merged mac80211 to resolve a
> conflict with the nl80211 fix. Anyway ...
>
> Here we have a few memory leak fixes related to BSS struct handling
> mostly from Ben, including a fix for a more theoretical problem
> (associating while a BSS struct times out) from myself, a compilation
> warning fix from Arend, mesh fixes from Thomas, tracking the beacon
> bitrate (Alex), a bandwidth change event fix (Ilan) and some initial
> work for 5/10 MHz channels from Simon.
>
> Let me know if there are any issues.
>
> johannes
>
>
> The following changes since commit 795d855d56c6d172f50a974f603ba923ac93ee76:
>
> mac80211: Fix rate control mask matching call (2013-06-12 09:12:43 +0200)
>
> 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 6c7c4cbfd5f59c04a40af67ad72d14e19215ef36:
>
> mac80211: initialize power mode for mesh STAs (2013-06-24 15:59:20 +0200)
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:[~2013-06-24 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 17:24 pull-request: mac80211-next 2013-06-24 Johannes Berg
2013-06-24 18:45 ` 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=20130624184520.GD1997@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.