diff options
| author |   Johannes Berg <johannes.berg@intel.com> | 2025-04-23 17:08:08 +0200 |
|---|---|---|
| committer |   Jakub Kicinski <kuba@kernel.org> | 2025-04-24 18:22:05 -0700 |
| commit | d57ee99831e336576359beb26e2b140511c99106 (patch) | |
| tree | ec5a6a2d86ed653509f8e3c8069858948c4c3088 | |
| parent | Merge branch 'tcp-fastopen-observability' (diff) | |
| download | wireguard-linux-d57ee99831e336576359beb26e2b140511c99106.tar.xz wireguard-linux-d57ee99831e336576359beb26e2b140511c99106.zip | |
net: ethernet: mtk_wed: annotate RCU release in attach()
There are some sparse warnings in wifi, and it seems that
it's actually possible to annotate a function pointer with
__releases(), making the sparse warnings go away. In a way
that also serves as documentation that rcu_read_unlock()
must be called in the attach method, so add that annotation.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Link: https://patch.msgid.link/20250423150811.456205-2-johannes@sipsolutions.net
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
| -rw-r--r-- | include/linux/soc/mediatek/mtk_wed.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/soc/mediatek/mtk_wed.h b/include/linux/soc/mediatek/mtk_wed.h index a476648858a6..d8949a4ed0dc 100644 --- a/include/linux/soc/mediatek/mtk_wed.h +++ b/include/linux/soc/mediatek/mtk_wed.h @@ -192,7 +192,7 @@ struct mtk_wed_device { }; struct mtk_wed_ops { - int (*attach)(struct mtk_wed_device *dev); + int (*attach)(struct mtk_wed_device *dev) __releases(RCU); int (*tx_ring_setup)(struct mtk_wed_device *dev, int ring, void __iomem *regs, bool reset); int (*rx_ring_setup)(struct mtk_wed_device *dev, int ring, |