Messages in this thread | | | Date | Mon, 22 Mar 2004 18:09:07 -0800 | From | William Lee Irwin III <> | Subject | Re: [PATCH] broken bitmap_parse for ncpus > 32 |
| |
At some point in the past, I wrote: >> Bugfixes are always good. Maybe the kerneldoc stuff would be a good idea >> for these functions, and the rest of the non-static functions ppl might >> be expected to call.
On Mon, Mar 22, 2004 at 07:14:33PM -0500, Joe Korty wrote: > IMO, one+ liners describing how a function is used is best put near > the function, where it is most likely to be seen. Stuff going into > Documentation/*.txt should be bulky stuff not suitable for inlining, > such as largish tutorials, annotated examples, theory papers, etc.
Sorry about not being clear; I meant the : and @ stuff I've seen around various comments that somehow gets yanked directly out of C comments in the source and generated into a pdf.
-- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |