Matthew Wilcox <willy@xxxxxxxxxxxxx> writes:
> kernel-doc is our own format, so sure, we can add whatever marker
> we want to it. I think it's not quite general enough because we have
> situations like:
>
> static inline void foo(int x)
> {
> numa_foo(x, NUMA_NO_NODE);
> };
>
> /**
> * foo - Frobnicate
> * @x: How many
> * @nid: Which node
> */
> void numa_foo(int x, int node)
> { .. }
>
> and now we're documenting a parameter that doesn't exist. The only
> solution is to move the kdoc to the header file, which is annoying for
> everyone. Or replicate the declaration in the C file and kdoc it there.
In this case, though, is there a reason to not document foo() as a
separate function?
jon
