From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/5] nl80211: fix validation of scheduled scan info for wowlan netdetect
Date: Fri, 27 Jan 2017 13:42:22 +0100 [thread overview]
Message-ID: <1485520942.5851.9.camel@sipsolutions.net> (raw)
In-Reply-To: <abafc8a5-1138-7c4f-66a3-d606700440cb@broadcom.com> (sfid-20170127_133812_465827_35DBEB56)
On Fri, 2017-01-27 at 13:38 +0100, Arend Van Spriel wrote:
>
> > IOW, I think Kalle can merge 2-5, and I can then pick up this one
> > when they hit net-next and I've synchronized, no?
>
> Agree.
Alright. I see you submitted another version, I'll assign 2-5 to Kalle,
and keep 1 for myself, and not worry about the ordering since I'm the
one to have to remember to actually apply it later :)
johannes
next prev parent reply other threads:[~2017-01-27 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 12:09 [PATCH 0/5] nl802111/brcmfmac: wowlan netdetect fixes Arend van Spriel
2017-01-27 12:09 ` [PATCH 1/5] nl80211: fix validation of scheduled scan info for wowlan netdetect Arend van Spriel
2017-01-27 12:31 ` Johannes Berg
2017-01-27 12:38 ` Arend Van Spriel
2017-01-27 12:42 ` Johannes Berg [this message]
2017-02-08 9:10 ` Johannes Berg
2017-02-08 9:56 ` Arend Van Spriel
2017-01-27 12:09 ` [PATCH 2/5] brcmfmac: provide a value for struct wowlan_support::max_nd_match_sets Arend van Spriel
2017-01-27 12:09 ` [PATCH 3/5] brcmfmac: fix handling firmware results for wowl netdetect Arend van Spriel
2017-01-27 12:09 ` [PATCH 4/5] brcmfmac: allow wowlan support to be per device Arend van Spriel
2017-01-27 12:22 ` Arend Van Spriel
2017-01-27 12:09 ` [PATCH 5/5] brcmfmac: add .update_connect_params() callback Arend van Spriel
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=1485520942.5851.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=kvalo@codeaurora.org \
--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).