From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org
Subject: Re: [PATCH v3 1/2] mac80211: cache mesh beacon
Date: Thu, 14 Feb 2013 20:54:17 +0100 [thread overview]
Message-ID: <1360871657.8210.14.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1360869614-29297-1-git-send-email-thomas@cozybit.com> (sfid-20130214_202134_927337_D6A0746D)
On Thu, 2013-02-14 at 11:20 -0800, Thomas Pedersen wrote:
> Previously, the entire mesh beacon would be generated each
> time the beacon timer fired. Instead generate a beacon
> head and tail (so the TIM can easily be inserted when mesh
> power save is on) when starting a mesh or the MBSS
> parameters change.
>
> Also add a mutex for protecting beacon updates and
> preventing leaks.
Applied both, hopefully for good this time ;-)
johannes
prev parent reply other threads:[~2013-02-14 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 19:20 [PATCH v3 1/2] mac80211: cache mesh beacon Thomas Pedersen
2013-02-14 19:20 ` [PATCH v3 2/2] mac80211: generate mesh probe responses Thomas Pedersen
2013-02-14 19:54 ` 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=1360871657.8210.14.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@cozybit.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