All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V3 1/9] nl80211: allow multiple active scheduled scan requests
Date: Wed, 26 Apr 2017 12:24:53 +0200	[thread overview]
Message-ID: <5bdba644-82db-9df1-bfac-14c707dbdfda@broadcom.com> (raw)
In-Reply-To: <1493197685.2464.15.camel@sipsolutions.net>



On 4/26/2017 11:08 AM, Johannes Berg wrote:
> On Wed, 2017-04-26 at 11:05 +0200, Arend van Spriel wrote:
>> I guess it could be done, but I'm tending towards doing that less
>>> again, I have no strong preference in this case. If it was
>>> something
>>> that seems likely to get abused, perhaps, but here...
>>
>> Ok. As long as drivers don't think they can use the list_head to push
>> it on a private list.
> 
> They'll crash immediately and be disabused of that notion :)
> 
>> The internal use comment does not end up in
>> kerneldoc. So maybe we can improve that? Would work for me.
> 
> It's difficult - though we could replace it with /* private: */ and
> remove those things from kernel-doc entirely.

probably won't work:

	/* internal */
	struct wiphy *wiphy;
	struct net_device *dev;
	unsigned long scan_start;
	struct rcu_head rcu_head;
	u32 owner_nlportid;

	/* keep last */
	struct ieee80211_channel *channels[0];
};

Regards,
Arend

  reply	other threads:[~2017-04-26 10:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 12:04 [PATCH V3 0/9] cfg80211: support multiple scheduled scans Arend van Spriel
2017-04-21 12:05 ` [PATCH V3 1/9] nl80211: allow multiple active scheduled scan requests Arend van Spriel
2017-04-25 19:49   ` Johannes Berg
2017-04-26  6:50     ` Johannes Berg
2017-04-26  8:46     ` Arend van Spriel
2017-04-26  8:49       ` Johannes Berg
2017-04-26  9:05         ` Arend van Spriel
2017-04-26  9:08           ` Johannes Berg
2017-04-26 10:24             ` Arend van Spriel [this message]
2017-04-21 12:05 ` [PATCH V3 2/9] nl80211: add support for BSSIDs in scheduled scan matchsets Arend van Spriel
2017-04-21 12:05 ` [PATCH V3 3/9] cfg80211: add request id parameter to .sched_scan_stop() signature Arend van Spriel
2017-04-21 12:05 ` [PATCH V3 4/9] cfg80211: add request id to cfg80211_sched_scan_*() api Arend van Spriel
2017-04-26  7:16   ` Johannes Berg
2017-04-26 18:18     ` Arend Van Spriel
2017-04-26 18:47       ` Johannes Berg
2017-04-21 12:05 ` [PATCH V3 5/9] brcmfmac: add firmware feature detection for gscan feature Arend van Spriel
2017-05-18 13:36   ` [V3, " Kalle Valo
2017-05-18 15:47     ` Kalle Valo
2017-05-18 19:34       ` Arend Van Spriel
2017-05-19  5:03         ` Kalle Valo
2017-04-21 12:05 ` [PATCH V3 6/9] brcmfmac: move scheduled scan wiphy param setting to pno module Arend van Spriel
2017-04-21 12:05 ` [PATCH V3 7/9] brcmfmac: add support multi-scheduled scan Arend van Spriel
2017-04-21 12:05 ` [PATCH V3 8/9] brcmfmac: add mutex to protect pno requests Arend van Spriel
2017-04-21 12:05 ` [PATCH V3 9/9] brcmfmac: add scheduled scan support for specified BSSIDs Arend van Spriel
2017-04-26  7:07 ` [PATCH V3 0/9] cfg80211: support multiple scheduled scans Johannes Berg

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=5bdba644-82db-9df1-bfac-14c707dbdfda@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --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 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.