If you want to know exactly what occurs, look at the code.
If you want an overview, a summary, a quick scan of the logic contained
within the code, and perhaps suggested best usage of the code, look at
the docs (if they exist).
The system I propose is entirely optional, and code can be documented
gradually, as developer time and outside contributions permit.
Regards,
Jeff
-- Custom driver development | Never worry about theory as long Open source programming | as the machinery does what it's | supposed to do. -- R. A. Heinlein- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/