From: Johannes Berg <johannes@sipsolutions.net>
To: Marco Porsch <marco@cozybit.com>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org
Subject: Re: [PATCHv2 0/6] mesh power save - basics
Date: Wed, 16 Jan 2013 12:32:13 +0100 [thread overview]
Message-ID: <1358335933.12297.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50F677B4.7040609@cozybit.com> (sfid-20130116_115641_363108_7D18C6FC)
On Wed, 2013-01-16 at 10:49 +0100, Marco Porsch wrote:
> Hi Johannes,
>
> I just checked back on the status of my patches and see no further
> comments while they are not applied yet. Is there anything odd about them?
No, I've just been very backlogged for a while ...
johannes
next prev parent reply other threads:[~2013-01-16 11:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 15:04 [PATCHv2 0/6] mesh power save - basics Marco Porsch
2013-01-07 15:04 ` [PATCHv2 1/6] nl80211: add range checks to mesh parameters Marco Porsch
2013-01-07 18:47 ` Thomas Pedersen
2013-01-07 15:04 ` [PATCHv2 2/6] mac80211: update mesh peer link counter during userspace peering Marco Porsch
2013-01-07 18:47 ` Thomas Pedersen
2013-01-07 15:04 ` [PATCHv2 3/6] mac80211: move add_tim to subfunction Marco Porsch
2013-01-07 15:04 ` [PATCHv2 4/6] {cfg,nl,mac}80211: set beacon interval and DTIM period on mesh join Marco Porsch
2013-01-07 15:04 ` [PATCHv2 5/6] {cfg,nl}80211: mesh power mode primitives and userspace access Marco Porsch
2013-01-07 15:04 ` [PATCHv2 6/6] mac80211: mesh power save basics Marco Porsch
2013-01-16 22:14 ` Johannes Berg
2013-01-17 14:08 ` Marco Porsch
2013-01-17 16:34 ` Marco Porsch
2013-01-18 11:52 ` Johannes Berg
2013-01-18 11:55 ` Marco Porsch
2013-01-16 9:49 ` [PATCHv2 0/6] mesh power save - basics Marco Porsch
2013-01-16 11:32 ` Johannes Berg [this message]
2013-01-16 21:57 ` Johannes Berg
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=1358335933.12297.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marco@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;
as well as URLs for NNTP newsgroup(s).