From: Greg KH <gregkh@linuxfoundation.org>
To: Jaewan Kim <jaewan@google.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, kernel-team@android.com,
adelva@google.com
Subject: Re: [PATCH v4 1/2] mac80211_hwsim: add PMSR capability support
Date: Sat, 21 Jan 2023 08:23:40 +0100 [thread overview]
Message-ID: <Y8uS/Bw3tnPoMIK2@kroah.com> (raw)
In-Reply-To: <20230120174934.3528469-2-jaewan@google.com>
On Fri, Jan 20, 2023 at 05:49:33PM +0000, Jaewan Kim wrote:
> This CL allows mac80211_hwsim to be configured with PMSR capability.
> The capability is mandatory because nl80211_pmsr_start() ignores
> incoming PMSR request if PMSR capability isn't set in the wiphy.
>
> This CL adds HWSIM_ATTR_PMSR_SUPPORT.
> It can be used to set PMSR capability when creating a new radio.
> To send extra details, HWSIM_ATTR_PMSR_SUPPORT can have nested
> PMSR capability attributes defined in the nl80211.h.
> Data format is the same as cfg80211_pmsr_capabilities.
>
> If HWSIM_ATTR_PMSR_SUPPORT is specified, mac80211_hwsim builds
> cfg80211_pmsr_capabilities and sets wiphy.pmsr_capa.
>
> Signed-off-by: Jaewan Kim <jaewan@google.com>
> ---
Always run scripts/checkpatch.pl on your submissions before sending them
in so you do not get grumpy maintainers asking you why you did not run
scripts/checkpatch.pl in your submission :(
next prev parent reply other threads:[~2023-01-21 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 17:49 [PATCH v4 0/2] mac80211_hwsim: Add PMSR support Jaewan Kim
2023-01-20 17:49 ` [PATCH v4 1/2] mac80211_hwsim: add PMSR capability support Jaewan Kim
2023-01-21 7:23 ` Greg KH [this message]
2023-01-20 17:49 ` [PATCH v4 2/2] mac80211_hwsim: handle FTM requests with virtio Jaewan Kim
2023-01-21 7:22 ` [PATCH v4 0/2] mac80211_hwsim: Add PMSR support Greg KH
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=Y8uS/Bw3tnPoMIK2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adelva@google.com \
--cc=jaewan@google.com \
--cc=johannes@sipsolutions.net \
--cc=kernel-team@android.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).