On 12.12.22 14:40, Johan Hovold wrote:
On Mon, Dec 12, 2022 at 02:27:46PM +0100, Oliver Neukum wrote:
On 12.12.22 14:14, Johan Hovold wrote:
On Mon, Dec 12, 2022 at 12:13:54PM +0100, Oliver Neukum wrote:
And in this case there was also no kernel doc for usb_get_intfdata()
which is equally self documenting. Why add redundant docs for only one
of these functions?
Because knowing that one of them exists makes the other much more
obvious.
I doubt anyone finds out about this function by reading generated kernel
documentation. You look at a driver, grep the function and look at the
single-line implementation.
Look, we cannot solve the issue whether kerneldoc is a good idea
in general here. If you want to open that can of worms on lkml,
by all means. go for it.
But failing that, silently eliminating it is just not nice.
But it was never perfectly good. It claims that a driver "should" use it,
when it may not need to (think simple driver using devres) and talks
If you are presented with an interface something needs to be done
specific to that interface.
about driver core resetting the pointer which is irrelevant.
But correct and topical. I am not arguing what people should or should
mot know.
If you just remove the last sentence, all will be well. And if you
insist replace "should" with "can".
Regards
Oliver
