From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC V3 0/5] cfg80211: support multiple scheduled scans
Date: Mon, 20 Feb 2017 11:55:22 +0100 [thread overview]
Message-ID: <1404cf52-b570-3dfb-031b-ba8eaa28ace1@broadcom.com> (raw)
In-Reply-To: <1487582393.5474.2.camel@sipsolutions.net>
On 20-2-2017 10:19, Johannes Berg wrote:
> On Wed, 2017-02-15 at 10:37 +0000, Arend van Spriel wrote:
>> Another review round for multiple scheduled scan support in nl80211.
>>
>
>
> Looks fine to me. Not sure I see much value in splitting patches 4/5,
> but whichever you prefer is fine with me.
I was a bit in doubt on granularity of the patches. Let's see what I
make of it when submitting a formal patch ;-)
> Maybe some of the commit messages ("It mainly illustrates ...") could
> use some rewording :)
Will do.
Thanks,
Arend
prev parent reply other threads:[~2017-02-20 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 10:37 [RFC V3 0/5] cfg80211: support multiple scheduled scans Arend van Spriel
2017-02-15 10:37 ` [RFC V3 1/5] nl80211: add request id in scheduled scan event messages Arend van Spriel
2017-02-15 10:37 ` [RFC V3 2/5] nl80211: allow multiple active scheduled scan requests Arend van Spriel
2017-02-15 10:37 ` [RFC V3 3/5] cfg80211: add request id parameter to .sched_scan_stop() signature Arend van Spriel
2017-02-15 10:37 ` [RFC V3 4/5] cfg80211: add request id to cfg80211_sched_scan_results() api Arend van Spriel
2017-02-15 10:37 ` [RFC V3 5/5] cfg80211: add request id in cfg80211_sched_scan_stopped{,_rtnl}() api Arend van Spriel
2017-02-20 9:19 ` [RFC V3 0/5] cfg80211: support multiple scheduled scans Johannes Berg
2017-02-20 10:55 ` Arend Van Spriel [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=1404cf52-b570-3dfb-031b-ba8eaa28ace1@broadcom.com \
--to=arend.vanspriel@broadcom.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).