Lines Matching full:documentation

3 How to help improve kernel documentation
6 Documentation is an important part of any software-development project.
7 Good documentation helps to bring new developers in and helps established
8 developers work more effectively.  Without top-quality documentation, a lot
12 Unfortunately, the kernel's documentation currently falls far short of what
16 Kernel documentation improvements can be made by developers at a variety of
19 documentation maintainer's list of tasks that most urgently need to be
22 The documentation TODO list
26 documentation to where it should be.  This list contains a number of
28 improve the documentation, please do not hold back!
33 The documentation build currently spews out an unbelievable number of
37 tasks on the documentation TODO list.  The task itself is reasonably
43 Warnings from the documentation build almost always point at a real
45 and fixing it at its source.  For this reason, patches fixing documentation
49 Another important point is that documentation warnings are often created by
50 problems in kerneldoc comments in C code.  While the documentation
52 documentation tree is often not the right one to actually carry those
55 For example, in a documentation build I grabbed a pair of warnings nearly
134 members or function parameters that lack documentation.  In such cases, it
138 from the documentation build, then we can start expecting developers to
147 generate links to that documentation.  Adding ``kernel-doc`` directives to
148 the documentation to bring those comments in can help the community derive
154 Note that the most value comes from pulling in the documentation for
157 documentation build unless they are placed in a document that is
164 Fixing typographical or formatting errors in the documentation is a quick
173    kernel documentation.  There is no need to fix one by replacing it with
177    is not to be debated in the context of kernel documentation.  Other
184 Ancient documentation
187 Some kernel documentation is current, maintained, and useful.  Some
188 documentation is ... not.  Dusty, old, and inaccurate documentation can
189 mislead readers and casts doubt on our documentation as a whole.  Anything
202 The best thing to do, of course, would be to bring the documentation
206 working to improve the documentation when asked nicely, and when their
209 Some documentation is beyond hope; we occasionally find documents that
211 There is surprising resistance to removing obsolete documentation, but we
212 should do that anyway.  Extra cruft in our documentation helps nobody.
226 Documentation coherency
230 the shelves in the 1990s.  They were simply collections of documentation
232 improved since then, but the kernel's documentation is still mostly built
235 kernel documentation; we have thousands of individual documents.
238 a set of "books" that group documentation for specific readers.  These
241  - Documentation/admin-guide/index.rst
242  - Documentation/core-api/index.rst
243  - Documentation/driver-api/index.rst
244  - Documentation/userspace-api/index.rst
246 As well as this book on documentation itself.
250 though.  Moving documentation files creates short-term pain for the people
286 work with that project to make rst2pdf work with the kernel documentation
289 Write more documentation