public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Baochen Qiang <quic_bqiang@quicinc.com>,
	Jeff Johnson <quic_jjohnson@quicinc.com>,
	ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 6/8] wifi: ath12k: support ARP and NS offload
Date: Mon, 03 Jun 2024 09:36:38 +0200	[thread overview]
Message-ID: <43680bd3c444da4c1b4e55b4ee4c7043c1186ccd.camel@sipsolutions.net> (raw)
In-Reply-To: <af326e49-df6e-4574-9562-44b6aee10abd@quicinc.com>

On Fri, 2024-05-31 at 13:11 +0800, Baochen Qiang wrote:
> 
> On 5/31/2024 11:42 AM, Baochen Qiang wrote:
> > > > +static void ath12k_wow_prepare_ns_offload(struct ath12k_vif *arvif,
> > > > +					  struct wmi_arp_ns_offload_arg *offload)
> > > > +{
> > > > +	struct inet6_dev *idev = arvif->idev;
> > > as noted above does it make more sense to get the netdev associated with the
> > > arvif and then use in6_dev_get(net_device) to get the inet6_dev rather than
> > > caching the pointer from the ipv6_addr_changed() callback?
> > Ah.. I didn't note that we can get inet6_dev in such a way, just thought the only way is to cache it in ipv6_changed() callback.
> > 
> > will get it using the following in next version:
> > 	struct ieee80211_vif *vif = container_of(arvif)
> > 	struct ieee80211_sub_if_data *sub_if_data = container_of(vif)
> > 	struct net_dev *ndev = sub_if_data->dev
> > 	struct inet6_dev *idev = in6_dev_get(ndev)
> Just found that ieee80211_sub_if_data is internal to mac80211, so not possible to get netdev in this way.
> 
> any other ideas on how to get netdev?

You can go via the wdev.

johannes


  parent reply	other threads:[~2024-06-03  7:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30  7:27 [PATCH v3 0/8] wifi: ath12k: add support for WoW Baochen Qiang
2024-05-30  7:27 ` [PATCH v3 1/8] wifi: ath12k: add ATH12K_DBG_WOW log level Baochen Qiang
2024-05-30 17:55   ` Jeff Johnson
2024-05-30 18:40     ` Kalle Valo
2024-05-30  7:27 ` [PATCH v3 2/8] wifi: ath12k: implement WoW enable and wakeup commands Baochen Qiang
2024-05-30  7:27 ` [PATCH v3 3/8] wifi: ath12k: add basic WoW functionalities Baochen Qiang
2024-05-30  7:27 ` [PATCH v3 4/8] wifi: ath12k: add WoW net-detect functionality Baochen Qiang
2024-06-20 11:10   ` Kalle Valo
2024-06-21  5:26     ` Baochen Qiang
2024-05-30  7:27 ` [PATCH v3 5/8] wifi: ath12k: implement hardware data filter Baochen Qiang
2024-05-30  7:27 ` [PATCH v3 6/8] wifi: ath12k: support ARP and NS offload Baochen Qiang
2024-05-30 18:26   ` Jeff Johnson
2024-05-31  3:42     ` Baochen Qiang
2024-05-31  3:49       ` Baochen Qiang
2024-05-31  5:11       ` Baochen Qiang
2024-05-31 17:26         ` Jeff Johnson
2024-06-03  2:47           ` Baochen Qiang
2024-06-03  2:48           ` Baochen Qiang
2024-06-03 14:22             ` Jeff Johnson
2024-06-03  9:32           ` Baochen Qiang
2024-06-03  7:36         ` Johannes Berg [this message]
2024-06-03  9:15           ` Baochen Qiang
2024-05-30  7:27 ` [PATCH v3 7/8] wifi: ath12k: support GTK rekey offload Baochen Qiang
2024-05-30  7:27 ` [PATCH v3 8/8] wifi: ath12k: handle keepalive during WoWLAN suspend and resume Baochen Qiang
2024-05-30 17:45 ` [PATCH v3 0/8] wifi: ath12k: add support for WoW Jeff Johnson

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=43680bd3c444da4c1b4e55b4ee4c7043c1186ccd.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_bqiang@quicinc.com \
    --cc=quic_jjohnson@quicinc.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