On Mon, 22 Jul 2019 15:24:33 -0700 Joe Perches <j...@perches.com> wrote:
> > If the functions themselves are fully defined in the .h file, I'd just add > > the kerneldoc there as well. That's how it's usually done, and you want > > to keep the documentation and the prototypes together. > > In this case, it's a macro and yes, the kernel-doc could > easily be set around the macro in the .h, but my desire > is to keep all the string function kernel-doc output > together so it should be added to lib/string.c > > Are you suggesting I move all the lib/string.c kernel-doc > to include/linux/string.h ? If you want the *output* together, just put the kernel-doc directives together in the RST file that pulls it all in. Or am I missing something here? Thanks, jon