Jonathan Corbet 3211ba4157 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.
2017-10-12 11:23:12 -06:00
2017-10-07 10:45:14 -06:00

Linux kernel
============

This file was moved to Documentation/admin-guide/README.rst

Please notice that there are several guides for kernel developers and users.
These guides can be rendered in a number of formats, like HTML and PDF.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
See Documentation/00-INDEX for a list of what is contained in each file.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.
Description
No description provided
Readme 3.4 GiB
Languages
C 97%
Assembly 1%
Shell 0.6%
Rust 0.5%
Python 0.4%
Other 0.3%