Right now, it is not possible to document nested struct and nested unions. kernel-doc simply ignore them. Add support to document them. This series starts with a patch getting rid of the now unused output formats for kernel-doc: since we got rid of all DocBook stuff, we should not need them anymore. The reason for dropping it (despite cleaning up), is that it doesn't make sense to invest time on adding new features for formats that aren't used anymore. The next 8 patches on this series improve kernel-doc documentation and finally get rid of its old documentation (kernel-doc-nano-HOWTO.txt). Patch 9/10 is the most interesting one in this series: it adds support for nested structures and unions. Patch 10/10 is just an example from a random header with kernel-doc markups. There's no special reason for selecting this file, and the comments there are likely wrong. So, please use it only as a way to test the new parser logic from patch 9/10. Mauro Carvalho Chehab (10): scripts: kernel-doc: get rid of unused output formats docs: kernel-doc.rst: better describe kernel-doc arguments docs: kernel-doc.rst: improve private members description docs: kernel-doc.rst: improve function documentation section docs: kernel-doc.rst: improve structs chapter docs: kernel-doc: improve typedef documentation docs: kernel-doc.rst: add documentation about man pages docs: get rid of kernel-doc-nano-HOWTO.txt scripts: kernel-doc: parse next structs/unions [RFC] w1_netlink.h: add support for nested structs --- Before this series, I send a few PoC patches. They were all replaced by patch 9/10. Documentation/00-INDEX | 2 - Documentation/doc-guide/kernel-doc.rst | 387 ++++++--- Documentation/kernel-doc-nano-HOWTO.txt | 322 -------- drivers/w1/w1_netlink.h | 4 + scripts/kernel-doc | 1304 ++----------------------------- 5 files changed, 346 insertions(+), 1673 deletions(-) delete mode 100644 Documentation/kernel-doc-nano-HOWTO.txt -- 2.13.5 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
