From mboxrd@z Thu Jan 1 00:00:00 1970 From: rpjday@crashcourse.ca (Robert P. J. Day) Date: Tue, 3 Feb 2015 09:50:07 -0500 (EST) Subject: why is "const u32 (*tab)[256]" not kerneldoc-able? In-Reply-To: <874mr3uk7e.fsf@nemi.mork.no> References: <87fvanuo9h.fsf@nemi.mork.no> <87bnlbuncq.fsf@nemi.mork.no> <874mr3uk7e.fsf@nemi.mork.no> Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Tue, 3 Feb 2015, Bj?rn Mork wrote: > "Robert P. J. Day" writes: > > > actually, i just found where this is a known issue: > > > > http://www.spinics.net/lists/linux-doc/msg09364.html > > Probably because it's a rare construct. > > But looking closer at this, trying to understand why the simple test > using > > scripts/kernel-doc lib/crc32.c |man -l - > > seemed to sort of work, I found that your main problem isn't really the > lack of kernel-doc support for array pointer parameters. It's a simple > mismatch between the documented and the exported functions. > > scripts/docproc will only generate docs for exported symbols. > lib/crc32.c has no documented *and* exported functions, and thats why > the output is empty. The array pointer is a red herring. ah, good point, i had totally missed that. i'll move this discussion to the linux-doc list and resolve it there. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================