Message ID | 20240506011637.27272-1-antonio@openvpn.net (mailing list archive) |
---|---|
Headers | show |
Series | Introducing OpenVPN Data Channel Offload | expand |
On Mon, 6 May 2024 03:16:13 +0200 Antonio Quartulli wrote: > I am finally back with version 3 of the ovpn patchset. > It took a while to address all comments I have received on v2, but I > am happy to say that I addressed 99% of the feedback I collected. Nice, one more check / warning that pops up is missing kdoc. W=1 build only catches kdoc problems in C sources, for headers try running something like: ./scripts/kernel-doc -none -Wall $new_files
On 08/05/2024 01:48, Jakub Kicinski wrote: > On Mon, 6 May 2024 03:16:13 +0200 Antonio Quartulli wrote: >> I am finally back with version 3 of the ovpn patchset. >> It took a while to address all comments I have received on v2, but I >> am happy to say that I addressed 99% of the feedback I collected. > > Nice, one more check / warning that pops up is missing kdoc. > W=1 build only catches kdoc problems in C sources, for headers > try running something like: > > ./scripts/kernel-doc -none -Wall $new_files I see there is one warning to fix due to a typ0 (eventS_wq vs event_wq), but I also get more warnings like this: drivers/net/ovpn/peer.h:119: warning: Function parameter or struct member 'vpn_addrs' not described in 'ovpn_peer' However vpn_addrs is an anonymous struct within struct ovpn_peer. I have already documented all its members using the form: @vpn_addrs.ipv4 @vpn_addrs.ipv6 Am I expected to document the vpn_addrs as well? Or is this a false positive? Regards,
On Wed, 8 May 2024 11:56:45 +0200 Antonio Quartulli wrote: > I see there is one warning to fix due to a typ0 (eventS_wq vs event_wq), > but I also get more warnings like this: > > drivers/net/ovpn/peer.h:119: warning: Function parameter or struct > member 'vpn_addrs' not described in 'ovpn_peer' > > However vpn_addrs is an anonymous struct within struct ovpn_peer. > I have already documented all its members using the form: > > @vpn_addrs.ipv4 > @vpn_addrs.ipv6 > > Am I expected to document the vpn_addrs as well? > Or is this a false positive? I think we need to trust the script on what's expected. The expectations around documenting anonymous structs may have changed recently, I remember fixing this in my code, too. BTW make sure you use -Wall, people started sending trivial patches to fix those :S Would be best not to add new ones.
On 09/05/2024 02:53, Jakub Kicinski wrote: > On Wed, 8 May 2024 11:56:45 +0200 Antonio Quartulli wrote: >> I see there is one warning to fix due to a typ0 (eventS_wq vs event_wq), >> but I also get more warnings like this: >> >> drivers/net/ovpn/peer.h:119: warning: Function parameter or struct >> member 'vpn_addrs' not described in 'ovpn_peer' >> >> However vpn_addrs is an anonymous struct within struct ovpn_peer. >> I have already documented all its members using the form: >> >> @vpn_addrs.ipv4 >> @vpn_addrs.ipv6 >> >> Am I expected to document the vpn_addrs as well? >> Or is this a false positive? > > I think we need to trust the script on what's expected. > The expectations around documenting anonymous structs may have > changed recently, I remember fixing this in my code, too. Alright, I will document those structs too then. > > BTW make sure you use -Wall, people started sending trivial > patches to fix those :S Would be best not to add new ones. eheh, rebase -exec is my friend :-) No warning shall pass! Thanks a lot,