From: Johannes Berg <johannes@sipsolutions.net>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Cc: linux-wireless@vger.kernel.org, Ilan Peer <ilan.peer@intel.com>,
Benjamin Berg <benjamin.berg@intel.com>
Subject: Re: [PATCH wireless-next 7/7] wifi: mac80211_hwsim: add NAN Instant Communication support
Date: Fri, 02 Oct 2026 09:26:04 +0200 [thread overview]
Message-ID: <8f58e34fa9962d3967dfa792fa2d724db89e4452.camel@sipsolutions.net> (raw)
In-Reply-To: <20261001162941.7e69a74a7ba5.Ib1a57bccf328a19dc55b914ccab73d023fe0876f@changeid>
On Thu, 2026-10-01 at 16:33 +0300, Miri Korenblit wrote:
> @@ -263,15 +300,26 @@ void mac80211_hwsim_nan_rx(struct ieee80211_hw *hw,
> slot = hwsim_nan_slot_from_tsf(rx_status.mactime);
> }
>
> + /* (overly) simplify things, only track 2.4 GHz here */
> + if (rx_status.freq != 2437)
> + return;
comments should generally help ... I see it removed below but maybe make
it better while touching it :)
> + scoped_guard(spinlock_bh, &data->nan.state_lock) {
> + /*
> + * Fall back to the device default if user space did not
> + * configure it
> + */
> + data->nan.discovery_beacon_interval =
> + conf->discovery_beacon_interval ? : 100;
That seems like the totally wrong place - should probably make that
default in cfg80211? Or is there a reason to believe it would need to be
device-specific?
> - data->nan.notify_dw = conf->enable_dw_notification;
Some of the refactoring in this commit is just confusing, like this just
disappearing. Please split the refactoring off first.
johannes
next prev parent reply other threads:[~2026-10-02 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:33 [PATCH wireless-next 0/7] wifi: cfg80211/mac80211: add NAN Instant Communication support Miri Korenblit
2026-10-01 13:33 ` [PATCH wireless-next 1/7] wifi: cfg80211: nan: add " Miri Korenblit
2026-10-01 13:33 ` [PATCH wireless-next 2/7] wifi: mac80211: nan: Update NAN configuration copy Miri Korenblit
2026-10-01 13:33 ` [PATCH wireless-next 3/7] wifi: cfg80211: nan: check Rx registration for NAN beacons Miri Korenblit
2026-10-02 7:03 ` Johannes Berg
2026-10-01 13:33 ` [PATCH wireless-next 4/7] wifi: mac80211: nan: allow " Miri Korenblit
2026-10-02 7:10 ` Johannes Berg
2026-10-04 12:40 ` Peer, Ilan
2026-10-01 13:33 ` [PATCH wireless-next 5/7] wifi: ieee80211: add NAN service ID list attribute definitions Miri Korenblit
2026-10-01 13:33 ` [PATCH wireless-next 6/7] wifi: mac80211_hwsim: nan: use ieee80211_is_nan_beacon() helper Miri Korenblit
2026-10-01 13:33 ` [PATCH wireless-next 7/7] wifi: mac80211_hwsim: add NAN Instant Communication support Miri Korenblit
2026-10-02 7:26 ` Johannes Berg [this message]
2026-10-04 13:12 ` Peer, Ilan
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=8f58e34fa9962d3967dfa792fa2d724db89e4452.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benjamin.berg@intel.com \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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