From: Kalle Valo <kvalo@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: aleksander.lobakin@intel.com, kuba@kernel.org,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
elder@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, nbd@nbd.name,
sean.wang@mediatek.com, Mark-MC.Lee@mediatek.com,
lorenzo@kernel.org, taras.chornyi@plvision.eu,
ath11k@lists.infradead.org, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org, geomatsi@gmail.com,
Jeff Johnson <jjohnson@kernel.org>,
quic_jjohnson@quicinc.com, leon@kernel.org,
dennis.dalessandro@cornelisnetworks.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, idosch@idosch.org,
angelogioacchino.delregno@collabora.com, matthias.bgg@gmail.com
Subject: Re: [PATCH net-next v7 10/10] wifi: ath11k: allocate dummy net_device dynamically
Date: Mon, 22 Apr 2024 16:08:44 +0300 [thread overview]
Message-ID: <87le55v92b.fsf@kernel.org> (raw)
In-Reply-To: <20240422123921.854943-11-leitao@debian.org> (Breno Leitao's message of "Mon, 22 Apr 2024 05:39:03 -0700")
Breno Leitao <leitao@debian.org> writes:
> Embedding net_device into structures prohibits the usage of flexible
> arrays in the net_device structure. For more details, see the discussion
> at [1].
>
> Un-embed the net_device from struct ath11k_ext_irq_grp by converting it
> into a pointer. Then use the leverage alloc_netdev() to allocate the
> net_device object at ath11k_ahb_config_ext_irq() for ahb, and
> ath11k_pcic_ext_irq_config() for pcic.
>
> The free of the device occurs at ath11k_ahb_free_ext_irq() for the ahb
> case, and ath11k_pcic_free_ext_irq() for the pcic case.
>
> [1] https://lore.kernel.org/all/20240229225910.79e224cf@kernel.org/
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> Tested-by: Kalle Valo <kvalo@kernel.org>
I assume this goes via net-next:
Acked-by: Kalle Valo <kvalo@kernel.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-04-22 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 12:38 [PATCH net-next v7 00/10] allocate dummy device dynamically Breno Leitao
2024-04-22 12:38 ` [PATCH net-next v7 01/10] net: core: Fix documentation Breno Leitao
2024-04-22 12:38 ` [PATCH net-next v7 02/10] net: free_netdev: exit earlier if dummy Breno Leitao
2024-04-22 12:38 ` [PATCH net-next v7 03/10] net: create a dummy net_device allocator Breno Leitao
2024-04-22 12:38 ` [PATCH net-next v7 04/10] net: marvell: prestera: allocate dummy net_device dynamically Breno Leitao
2024-04-22 12:38 ` [PATCH net-next v7 05/10] net: mediatek: mtk_eth_sock: " Breno Leitao
2024-04-22 12:38 ` [PATCH net-next v7 06/10] net: ipa: " Breno Leitao
2024-04-22 12:39 ` [PATCH net-next v7 07/10] net: ibm/emac: " Breno Leitao
2024-04-22 12:39 ` [PATCH net-next v7 08/10] wifi: qtnfmac: Use netdev dummy allocator helper Breno Leitao
2024-04-22 13:07 ` Kalle Valo
2024-04-22 12:39 ` [PATCH net-next v7 09/10] wifi: ath10k: allocate dummy net_device dynamically Breno Leitao
2024-04-22 13:08 ` Kalle Valo
2024-04-22 12:39 ` [PATCH net-next v7 10/10] wifi: ath11k: " Breno Leitao
2024-04-22 13:08 ` Kalle Valo [this message]
2024-04-24 11:10 ` [PATCH net-next v7 00/10] allocate dummy device dynamically patchwork-bot+netdevbpf
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=87le55v92b.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Mark-MC.Lee@mediatek.com \
--cc=aleksander.lobakin@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=geomatsi@gmail.com \
--cc=idosch@idosch.org \
--cc=jjohnson@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=leon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_jjohnson@quicinc.com \
--cc=sean.wang@mediatek.com \
--cc=taras.chornyi@plvision.eu \
/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;
as well as URLs for NNTP newsgroup(s).