From: Johannes Berg <johannes@sipsolutions.net>
To: Ria Thomas <ria.thomas@morsemicro.com>
Cc: linux-wireless@vger.kernel.org, lachlan.hodges@morsemicro.com,
arien.judge@morsemicro.com, pradeep.reddy@morsemicro.com,
simon@morsemicro.com
Subject: Re: [PATCH wireless-next v2 1/3] wifi: cfg80211: Add support for S1G Response Indication Configuration
Date: Tue, 17 Feb 2026 12:41:48 +0100 [thread overview]
Message-ID: <ed4316fdadf5b25e9e27df355ea14eee1efd7181.camel@sipsolutions.net> (raw)
In-Reply-To: <20260212084351.aqswgnvnuepun6em@1207> (sfid-20260212_094358_698471_E6882E0E)
Hi,
> > But we still need to decide where it should live, although in
> > that case I'd be more willing to accept an interface setting despite
> > the lifetime issues.)
> >
>
> We think it makes the most sense to treat Response Indication as an
> interface-level setting as it avoids introducing peer-specific state
> that is neither negotiated nor maintained by the protocol.
Fair. I don't really think it makes a huge difference - this state is
not negotiated nor maintained by the protocol at the interface level
either, after all :-) In a way I don't think it's a good argument either
way I guess, but if it's only a debug config I also don't care much (and
we already have things like tkip_mic_test that are in a way similar.)
> That said as the response indication is only a test configuration there
> is expected to be some changes to the upcoming patches. I would preferably
> submit the response indication configuration as a single patch and NDP
> ADDBA/DELBA negotiations as a different patch. This would open up two different
> new mail chains for two patches which is different from the current one.
Sure, if it can be separated I have no issues with that.
johannes
next prev parent reply other threads:[~2026-02-17 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 6:24 [PATCH wireless-next v2 0/3] wifi: add S1G response indication configuration with NDP BA support Ria Thomas
2025-12-09 6:24 ` [PATCH wireless-next v2 1/3] wifi: cfg80211: Add support for S1G Response Indication Configuration Ria Thomas
2026-01-08 12:27 ` Johannes Berg
2026-01-09 4:00 ` Ria Thomas
2026-01-13 8:50 ` Johannes Berg
2026-01-16 5:31 ` Ria Thomas
2026-02-06 6:11 ` Ria Thomas
2026-02-06 7:57 ` Johannes Berg
2026-02-12 8:43 ` Ria Thomas
2026-02-17 11:41 ` Johannes Berg [this message]
2025-12-09 6:24 ` [PATCH wireless-next v2 2/3] wifi: mac80211: track S1G Response Indication (RI) and notify drivers Ria Thomas
2025-12-09 6:24 ` [PATCH wireless-next v2 3/3] wifi: mac80211: add support for NDP ADDBA/DELBA for S1G Ria Thomas
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=ed4316fdadf5b25e9e27df355ea14eee1efd7181.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arien.judge@morsemicro.com \
--cc=lachlan.hodges@morsemicro.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeep.reddy@morsemicro.com \
--cc=ria.thomas@morsemicro.com \
--cc=simon@morsemicro.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