From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/6] brcmfmac: extend wowl and cleanup
Date: Fri, 08 Jan 2016 10:47:06 +0200 [thread overview]
Message-ID: <87bn8wjw51.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <568EEF26.2060401@broadcom.com> (Arend van Spriel's message of "Fri, 8 Jan 2016 00:05:10 +0100")
Arend van Spriel <arend@broadcom.com> writes:
> On 01/05/2016 11:05 AM, Arend van Spriel wrote:
>> This smallish series contains:
>> * link down fix for IBSS.
>> * support wowl upon net detect.
>> * cleanup timeout definitions.
>>
>> The series are intended for 4.5 kernel and apply to
>> the master branch of wireless-drivers-next repo on top
>> of series posted earlier with Message-ID:
>>
>> <1451724102-21911-1-git-send-email-arend@broadcom.com>
>
> Hi Kalle,
>
> Is this one I send last tuesday going to make it. I did not get any
> remarks on these patches so.. pretty please ;-)
Hehe :) I have to admit that I was about to postpone these to 4.6 but
these are actually so simple so I took them anyway.
--
Kalle Valo
prev parent reply other threads:[~2016-01-08 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 10:05 [PATCH 0/6] brcmfmac: extend wowl and cleanup Arend van Spriel
2016-01-05 10:05 ` [PATCH 1/6] brcmfmac: Add wowl net detect support Arend van Spriel
2016-01-08 8:45 ` [1/6] " Kalle Valo
2016-01-05 10:05 ` [PATCH 2/6] brcmfmac: Reshuffle functions to avoid forward declarations Arend van Spriel
2016-01-05 10:05 ` [PATCH 3/6] brcmfmac: change brcmf_sdio_wd_timer() prototype Arend van Spriel
2016-01-05 10:05 ` [PATCH 4/6] brcmfmac: use msecs_to_jiffies() in macro definitions Arend van Spriel
2016-01-05 10:05 ` [PATCH 5/6] brcmfmac: use jiffies for timeout in btcoex Arend van Spriel
2016-01-05 10:05 ` [PATCH 6/6] brcmfmac: Do not handle link downs for ibss Arend van Spriel
2016-01-07 23:05 ` [PATCH 0/6] brcmfmac: extend wowl and cleanup Arend van Spriel
2016-01-08 8:47 ` Kalle Valo [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=87bn8wjw51.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend@broadcom.com \
--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).