summaryrefslogtreecommitdiff
path: root/Documentation/cdrom
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2017-10-12 11:23:12 -0600
committerJonathan Corbet <corbet@lwn.net>2017-10-12 11:23:12 -0600
commit3211ba4157b547c182058711d1ad4a418df5d6e9 (patch)
tree454db16eafdf375d0eaedf8c800d56fa85b66a5c /Documentation/cdrom
parente8939222dced668fc5cae02b0b601af069801107 (diff)
parentf2b41874240411a7d06aac2dc864a389c93183cc (diff)
Merge branch 'refs' into docs-next
Tom Saeger says: Recently, while reading up on binfmt I attempted to open a document ref only to find it was invalid. I did a quick grep, found all the binfmt_misc related broken refs and sent a patch. Fine. Easy. Then I wondered, "how many broken doc refs are there?". Turns out with all the recent doc moves, quite a few. I went about fixing just those found in Documentation/, except those in Documentation/translations/ and Documentation/devicetree/ for now. Most of these changes were s/txt/rst/ or fixing up a path to an obvious new location. Some required going back to v4.10 v4.4 or some other version to sleuth-out what content was actually being referenced and then fixing the reference to point to the new file with that content.
Diffstat (limited to 'Documentation/cdrom')
0 files changed, 0 insertions, 0 deletions