From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Luca Coelho <luca@coelho.fi>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] nl80211: fix validation of scheduled scan info for wowlan netdetect
Date: Fri, 27 Jan 2017 12:27:08 +0100 [thread overview]
Message-ID: <1485516428.5851.6.camel@sipsolutions.net> (raw)
In-Reply-To: <a36abf1d-5d4b-4c37-e325-a69166663a04@broadcom.com> (sfid-20170127_122523_881598_29BEDE90)
> I actually have two dependent brcmfmac patches. Do you expect
> conflict if Kalle takes all?
Not really, if that's somehow easier we can do that.
johannes
next prev parent reply other threads:[~2017-01-27 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 10:01 [PATCH] nl80211: fix validation of scheduled scan info for wowlan netdetect Arend van Spriel
2017-01-19 12:00 ` Luca Coelho
2017-01-19 13:08 ` Arend Van Spriel
2017-01-24 8:57 ` Johannes Berg
2017-01-24 11:28 ` Arend Van Spriel
2017-01-27 11:25 ` Arend Van Spriel
2017-01-27 11:27 ` Johannes Berg [this message]
2017-01-27 11:29 ` 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=1485516428.5851.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--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).