From: "Rafał Miłecki" <zajec5@gmail.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
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 13:29:19 +0100 [thread overview]
Message-ID: <CACna6rx20tvodySME7+oeSbp_MmLDBta0C92tihEVK3GJkJ77w@mail.gmail.com> (raw)
In-Reply-To: <f0329a78-abdc-020a-5362-7b3e6b772593@broadcom.com>
On 29 November 2016 at 10:23, Arend Van Spriel
<arend.vanspriel@broadcom.com> wrote:
> On 29-11-2016 8:57, Johannes Berg wrote:
>> On Tue, 2016-11-29 at 08:08 +0100, Rafa=C5=82 Mi=C5=82ecki 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?)
>
> Yeah. The module is called pfn in our firmware, which stands for
> preferred network. So not sure whether it was a BRCM term morphed into
> Android term or vice versa.
>
> Kalle,
>
> If needed I could drop the use of the term and resubmit the series.
I don't have anything against it, I was just trying to understand that
part of driver (which makes more sense now, thanks).
--=20
Rafa=C5=82
next prev parent reply other threads:[~2016-11-29 12:29 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
2016-11-29 9:23 ` Arend Van Spriel
2016-11-29 12:29 ` Rafał Miłecki [this message]
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=CACna6rx20tvodySME7+oeSbp_MmLDBta0C92tihEVK3GJkJ77w@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=johannes@sipsolutions.net \
--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).