Re: [PATCH net-next v3 07/24] ovpn: introduce the ovpn_peer object

On Fri, 10 May 2024 20:57:33 +0200 Antonio Quartulli wrote:

quoted

I suspect it is more complex than that. checkpatch does not understand
kdoc. It just knows the rule that there should be a comment next to a
lock, hopefully indicating what the lock protects. In order to fix
this, checkpatch would need to somehow invoke the kdoc parser, and ask
it if the lock has kdoc documentation.

I suspect we are just going to have to live with this.  

since we are now requiring new code to always have kdoc, can't we just 
drop the checkpatch warning?

I don't think we require kdoc, but I agree that the warning is rather
ineffective.