From: Johannes Berg <johannes@sipsolutions.net>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH iw v2 0/4] iw: add scheduled scan support
Date: Tue, 17 Mar 2015 16:10:33 +0100 [thread overview]
Message-ID: <1426605033.1985.48.camel@sipsolutions.net> (raw)
In-Reply-To: <1426601510-8251-1-git-send-email-luca@coelho.fi>
On Tue, 2015-03-17 at 16:11 +0200, Luca Coelho wrote:
> From: Luciano Coelho <luciano.coelho@intel.com>
>
> This series adds scheduled scan support to the iw tool (finally! ;).
>
> In v2, just rebased.
Great, thanks; all applied.
johannes
prev parent reply other threads:[~2015-03-17 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 14:11 [PATCH iw v2 0/4] iw: add scheduled scan support Luca Coelho
2015-03-17 14:11 ` [PATCH iw v2 1/4] iw: move generic sched scan parsing code out of net detect Luca Coelho
2015-03-17 14:11 ` [PATCH iw v2 2/4] iw: implement scheduled scan Luca Coelho
2015-03-17 14:11 ` [PATCH iw v2 3/4] iw: add support for active " Luca Coelho
2015-03-17 14:11 ` [PATCH iw v2 4/4] iw: add randomise option for sched_scan Luca Coelho
2015-03-17 15:10 ` 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=1426605033.1985.48.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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).