Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 wireless-next 03/15] wifi: nl80211/cfg80211: support stations of non-netdev interfaces
Date: Thu, 19 Feb 2026 17:24:25 -0800	[thread overview]
Message-ID: <68db44c5-0a81-4451-bbb4-1e211d6b7cde@oss.qualcomm.com> (raw)
In-Reply-To: <20260219114327.65c9cc96f814.Ic02066b88bb8ad6b21e15cbea8d720280008c83b@changeid>

On 2/19/2026 1:47 AM, Miri Korenblit wrote:
> diff --git a/drivers/net/wireless/ath/ath6kl/cfg80211.c b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> index 88f0197fc041..eecba2201b10 100644
> --- a/drivers/net/wireless/ath/ath6kl/cfg80211.c
> +++ b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> @@ -1775,9 +1775,10 @@ static bool is_rate_ht40(s32 rate, u8 *mcs, bool *sgi)
>  	return false;
>  }
>  
> -static int ath6kl_get_station(struct wiphy *wiphy, struct net_device *dev,
> +static int ath6kl_get_station(struct wiphy *wiphy, struct wireless_dev *wdev,
>  			      const u8 *mac, struct station_info *sinfo)
>  {
> +	struct net_device *dev = wdev->netdev;

with the upcoming logic will it ever be possible that wdev->netdev is NULL?
just want to make sure everything is still safe

>  	struct ath6kl *ar = ath6kl_priv(dev);
>  	struct ath6kl_vif *vif = netdev_priv(dev);
>  	long left;

  reply	other threads:[~2026-02-20  1:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  9:47 [PATCH v4 wireless-next 00/15] wifi: cfg80211/nl80211: Add NAN Data Path support Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 01/15] wifi: nl80211: refactor nl80211_parse_chandef Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 02/15] wifi: cfg80211: remove unneeded call to cfg80211_leave Miri Korenblit
2026-02-20  1:15   ` Jeff Johnson
2026-02-19  9:47 ` [PATCH v4 wireless-next 03/15] wifi: nl80211/cfg80211: support stations of non-netdev interfaces Miri Korenblit
2026-02-20  1:24   ` Jeff Johnson [this message]
2026-02-20 11:22     ` Korenblit, Miriam Rachel
2026-02-19  9:47 ` [PATCH v4 wireless-next 04/15] wifi: cfg80211: refactor wiphy_suspend Miri Korenblit
2026-02-20  1:25   ` Jeff Johnson
2026-02-19  9:47 ` [PATCH v4 wireless-next 05/15] wifi: nl80211: don't allow DFS channels for NAN Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 06/15] wifi: cfg80211: Add an API to configure local NAN schedule Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 07/15] wifi: cfg80211: make sure NAN chandefs are valid Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 08/15] wifi: cfg80211: add support for NAN data interface Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 09/15] wifi: cfg80211: separately store HT, VHT and HE capabilities for NAN Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 10/15] wifi: nl80211: add support for NAN stations Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 11/15] wifi: nl80211: define an API for configuring the NAN peer's schedule Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 12/15] wifi: cfg80211: allow ToDS=0/FromDS=0 data frames on NAN data interfaces Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 13/15] wifi: nl80211: allow reporting spurious NAN Data frames Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 14/15] wifi: nl80211: add NL80211_CMD_NAN_ULW_UPDATE notification Miri Korenblit
2026-02-19  9:47 ` [PATCH v4 wireless-next 15/15] wifi: nl80211: Add a notification to notify NAN channel evacuation Miri Korenblit

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=68db44c5-0a81-4451-bbb4-1e211d6b7cde@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.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