public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Peddolla Harshavardhan Reddy <peddolla.reddy@oss.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 05/13] wifi: nl80211/cfg80211: add peer measurement abort command
Date: Wed, 4 Mar 2026 12:29:38 +0530	[thread overview]
Message-ID: <63102b0f-bd91-44cb-856d-ef0f51ba76b6@oss.qualcomm.com> (raw)
In-Reply-To: <8dd352f984cfd23ed178d5917419e15af0c201e7.camel@sipsolutions.net>


On 30-Jan-26 9:45 PM, Johannes Berg wrote:
> On Fri, 2026-01-30 at 21:30 +0530, Peddolla Harshavardhan Reddy wrote:
>> Add support for aborting ongoing peer measurement sessions
>> through a new NL80211_CMD_PEER_MEASUREMENT_ABORT command.
>> This allows userspace to cancel continuous ranging or other
>> long-running measurement sessions before completion.
>>
>> The abort operation is identified by the measurement cookie.
>> When a matching request is found, it is marked for cleanup
>> and the existing free work is scheduled to handle the
>> abortion and notify the driver.
> Originally, the idea was that we don't need this, since it's easy to
> just close the socket. Are there any resource constraints in socket
> handling in userspace that make this necessary? I'm not necessarily
> totally opposed to this, but you also haven't explained why it's
> necessary at all.
>
> johannes

We’ll be dropping this. As you pointed out, PMSR abort can be handled by closing the socket. Thanks.



  reply	other threads:[~2026-03-04  6:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 16:00 [PATCH 00/13] Ranging support enhancements Peddolla Harshavardhan Reddy
2026-01-30 16:00 ` [PATCH 01/13] wifi: nl80211/cfg80211: Allow RSTA role to be enabled without LMR request Peddolla Harshavardhan Reddy
2026-02-02 14:46   ` Jeff Johnson
2026-01-30 16:00 ` [PATCH 02/13] wifi: nl80211/cfg80211: add proximity detection capabilities to PMSR Peddolla Harshavardhan Reddy
2026-01-30 16:00 ` [PATCH 03/13] wifi: nl80211/cfg80211: add continuous ranging and PD request support Peddolla Harshavardhan Reddy
2026-02-01  0:52   ` Jeff Johnson
2026-01-30 16:00 ` [PATCH 04/13] wifi: nl80211/cfg80211: extend PMSR FTM response for proximity ranging Peddolla Harshavardhan Reddy
2026-01-30 16:00 ` [PATCH 05/13] wifi: nl80211/cfg80211: add peer measurement abort command Peddolla Harshavardhan Reddy
2026-01-30 16:15   ` Johannes Berg
2026-03-04  6:59     ` Peddolla Harshavardhan Reddy [this message]
2026-01-30 16:00 ` [PATCH 06/13] wifi: nl80211/cfg80211: add role-based PD peer limits Peddolla Harshavardhan Reddy
2026-02-02 17:22   ` Vasanthakumar Thiagarajan
2026-01-30 16:00 ` [PATCH 07/13] wifi: nl80211/cfg80211: add ingress/egress distance thresholds for FTM Peddolla Harshavardhan Reddy
2026-02-02 14:55   ` Jeff Johnson
2026-01-30 16:00 ` [PATCH 08/13] wifi: nl80211/cfg80211: add PD-specific bandwidth capabilities " Peddolla Harshavardhan Reddy
2026-02-02 14:56   ` Jeff Johnson
2026-01-30 16:00 ` [PATCH 09/13] wifi: nl80211/cfg80211: add FTM range report negotiation support Peddolla Harshavardhan Reddy
2026-02-02 14:57   ` Jeff Johnson
2026-01-30 16:00 ` [PATCH 10/13] wifi: nl80211/cfg80211: add result reporting control for PD requests Peddolla Harshavardhan Reddy
2026-02-02 14:58   ` Jeff Johnson
2026-01-30 16:00 ` [PATCH 11/13] wifi: nl80211/cfg80211: add MAC randomization support " Peddolla Harshavardhan Reddy
2026-02-02 14:59   ` Jeff Johnson
2026-02-02 17:33   ` Vasanthakumar Thiagarajan
2026-01-30 16:00 ` [PATCH 12/13] wifi: nl80211/cfg80211: add LTF keyseed support for secure ranging Peddolla Harshavardhan Reddy
2026-02-01  0:50   ` Jeff Johnson
2026-02-02 17:36   ` Vasanthakumar Thiagarajan
2026-01-30 16:00 ` [PATCH 13/13] mac80211_hwsim: Add support for extended FTM ranging Peddolla Harshavardhan Reddy
2026-01-30 18:52 ` [PATCH 00/13] Ranging support enhancements Jeff Johnson
2026-02-02 17:44 ` Vasanthakumar Thiagarajan
2026-02-03 11:40 ` Lachlan Hodges
2026-03-04  7:01   ` Peddolla Harshavardhan Reddy

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=63102b0f-bd91-44cb-856d-ef0f51ba76b6@oss.qualcomm.com \
    --to=peddolla.reddy@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox