summaryrefslogtreecommitdiffstats
path: root/Documentation/admin-guide
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2018-02-20 12:29:50 -0700
committerJonathan Corbet <corbet@lwn.net>2018-02-20 12:29:50 -0700
commitfcdf1df2032c6f12f86d71feef29cf1cfbcee758 (patch)
tree80023f86e4ec878bee2a236f8a93f7ec8f93f88d /Documentation/admin-guide
parent281a7af87352011fa5a28e3cf6ce601dec79a179 (diff)
parent3847637840def5d7c890acecb2a8ee8242d958dc (diff)
downloadlinux-0-day-fcdf1df2032c6f12f86d71feef29cf1cfbcee758.tar.gz
linux-0-day-fcdf1df2032c6f12f86d71feef29cf1cfbcee758.tar.xz
Merge branch 'kerneldoc2' into docs-next
So once upon a time I set out to fix the problem reported by Tobin wherein a literal block within a kerneldoc comment would be corrupted in processing. On the way, though, I got annoyed at the way I have to learn how kernel-doc works from the beginning every time I tear into it. As a result, seven of the following eight patches just get rid of some dead code and reorganize the rest - mostly turning the 500-line process_file() function into something a bit more rational. Sphinx output is unchanged after these are applied. Then, at the end, there's a tweak to stop messing with literal blocks. If anybody was unaware that I've not done any serious Perl since the 1990's, they will certainly understand that fact now.
Diffstat (limited to 'Documentation/admin-guide')
0 files changed, 0 insertions, 0 deletions