From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Arend van Spriel" <arend.vanspriel@broadcom.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 03/12] brcmfmac: move pno helper functions in separate source file
Date: Tue, 29 Nov 2016 08:57:47 +0100 [thread overview]
Message-ID: <1480406267.10012.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CACna6rwSDT1UeuexMpNhVMxKHWpZGdzDg7C1b5wVOhXzO3o=MA@mail.gmail.com> (sfid-20161129_080814_911793_E1764CEC)
On Tue, 2016-11-29 at 08:08 +0100, Rafał Miłecki wrote:
> On 23 November 2016 at 11:25, Arend van Spriel
> <arend.vanspriel@broadcom.com> wrote:
> >
> > Introducing new source file for pno related functionality. Moving
> > existing pno functions.
>
> Let me ask one basic question as I'm curious: what that PNO stands
> for? I couldn't find it explained in the code.
It's an Android term - Preferred Network Offload(ing?)
johannes
next prev parent reply other threads:[~2016-11-29 7:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 10:25 [PATCH 00/12] brcmfmac: scheduled scan cleanup and chip support Arend van Spriel
2016-11-23 10:25 ` [PATCH 01/12] brcmfmac: add pcie host dongle interface rev6 support Arend van Spriel
2016-11-29 15:30 ` [01/12] " Kalle Valo
2016-11-23 10:25 ` [PATCH 02/12] brcmfmac: add support for 43341 chip Arend van Spriel
2016-11-23 10:25 ` [PATCH 03/12] brcmfmac: move pno helper functions in separate source file Arend van Spriel
2016-11-29 7:08 ` Rafał Miłecki
2016-11-29 7:57 ` Johannes Berg [this message]
2016-11-29 9:23 ` Arend Van Spriel
2016-11-29 12:29 ` Rafał Miłecki
2016-11-29 14:54 ` Kalle Valo
2016-11-23 10:25 ` [PATCH 04/12] brcmfmac: fix handling ssids in .sched_scan_start() callback Arend van Spriel
2016-11-23 10:25 ` [PATCH 05/12] brcmfmac: change prototype for brcmf_do_escan() Arend van Spriel
2016-11-23 10:25 ` [PATCH 06/12] brcmfmac: make internal escan more generic Arend van Spriel
2016-11-23 10:25 ` [PATCH 07/12] brcmfmac: split up brcmf_pno_config() function Arend van Spriel
2016-11-23 10:25 ` [PATCH 08/12] brcmfmac: move scheduled scan activation to pno source file Arend van Spriel
2016-11-23 10:25 ` [PATCH 09/12] brcmfmac: use provided channels for scheduled scan Arend van Spriel
2016-11-23 10:25 ` [PATCH 10/12] brcmfmac: remove restriction from .sched_scan_start() callback Arend van Spriel
2016-11-23 10:25 ` [PATCH 11/12] brcmfmac: use requested scan interval in scheduled scan Arend van Spriel
2016-11-23 10:25 ` [PATCH 12/12] brcmfmac: fix scheduled scan result handling for newer chips Arend van Spriel
2016-11-29 7:37 ` [PATCH 00/12] brcmfmac: scheduled scan cleanup and chip support Rafał Miłecki
2016-11-29 9:58 ` Arend Van Spriel
2016-11-29 12:30 ` Rafał Miłecki
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=1480406267.10012.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.