linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
	Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
	Lior David <liord@codeaurora.org>,
	luca@coelho.fi, Etan Cohen <etancohen@google.com>,
	Roy Want <roywant@google.com>,
	Arend Van Spriel <arend.vanspriel@broadcom.com>,
	Franky Lin <franky.lin@broadcom.com>
Subject: Re: [RFC v3] cfg80211: add peer measurement with FTM API
Date: Mon, 29 Oct 2018 16:56:33 +0200	[thread overview]
Message-ID: <87d0rser8e.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <b0a738370519c5de534769ed93152575b756083e.camel@sipsolutions.net> (Johannes Berg's message of "Mon, 15 Oct 2018 09:29:59 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Sat, 2018-10-13 at 12:55 +0300, Kalle Valo wrote:
>> 
>> >  struct cfg80211_ops {
>> >  	int	(*suspend)(struct wiphy *wiphy, struct cfg80211_wowlan *wow);
>> 
>> It would be nice to document if these ops can sleep or not.
>
> I don't think we've documented that *anywhere* in cfg80211, but
> everything can sleep there ...
>
> At the mac80211 level things are different, so there we do document a
> case-by-case basis.

Makes sense, sorry for the noise.

-- 
Kalle Valo

  reply	other threads:[~2018-10-29 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 10:08 [RFC v3] cfg80211: add peer measurement with FTM API Johannes Berg
2018-10-12 10:32 ` Arend van Spriel
2018-10-12 10:41   ` Johannes Berg
2018-10-12 10:48     ` Arend van Spriel
2018-10-13  9:55 ` Kalle Valo
2018-10-15  7:29   ` Johannes Berg
2018-10-29 14:56     ` Kalle Valo [this message]
2018-10-16  9:15 ` 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=87d0rser8e.fsf@qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=etancohen@google.com \
    --cc=franky.lin@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=liord@codeaurora.org \
    --cc=luca@coelho.fi \
    --cc=pradeepc@codeaurora.org \
    --cc=roywant@google.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 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).