Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 3211ba41 authored by Jonathan Corbet's avatar Jonathan Corbet
Browse files

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.
parents e8939222 f2b41874

Documentation/ABI/stable/sysfs-devices

+1 −1
Original line number Diff line number Diff line 
# Note: This documents additional properties of any device beyond what

# is documented in Documentation/sysfs-rules.txt

# is documented in Documentation/admin-guide/sysfs-rules.rst



What:		/sys/devices/*/of_node

Date:		February 2015

Documentation/ABI/testing/evm

+2 −2
Original line number Diff line number Diff line
@@ -18,6 +18,6 @@ Description: 
		in the initramfs, which has already been measured as part

		of the trusted boot.  For more information on creating and

		loading existing trusted/encrypted keys, refer to:

		Documentation/keys-trusted-encrypted.txt.  (A sample dracut

		patch, which loads the trusted/encrypted key and enables

		Documentation/security/keys/trusted-encrypted.rst.  (A sample

		dracut patch, which loads the trusted/encrypted key and enables

		EVM, is available from http://linux-ima.sourceforge.net/#EVM.)

Documentation/ABI/testing/sysfs-devices-system-cpu

+4 −2
Original line number Diff line number Diff line
@@ -187,7 +187,8 @@ Description: Processor frequency boosting control 
		This switch controls the boost setting for the whole system.

		Boosting allows the CPU and the firmware to run at a frequency

		beyound it's nominal limit.

		More details can be found in Documentation/cpu-freq/boost.txt

		More details can be found in

		Documentation/admin-guide/pm/cpufreq.rst





What:		/sys/devices/system/cpu/cpu#/crash_notes
@@ -223,7 +224,8 @@ Description: Parameters for the Intel P-state driver 
		no_turbo: limits the driver to selecting P states below the turbo

		frequency range.



		More details can be found in Documentation/cpu-freq/intel-pstate.txt

		More details can be found in

		Documentation/admin-guide/pm/intel_pstate.rst



What:		/sys/devices/system/cpu/cpu*/cache/index*/<set_of_attributes_mentioned_below>

Date:		July 2014(documented, existed before August 2008)

Documentation/ABI/testing/sysfs-power

+4 −2
Original line number Diff line number Diff line
@@ -18,7 +18,8 @@ Description: 
		Writing one of the above strings to this file causes the system

		to transition into the corresponding state, if available.



		See Documentation/power/states.txt for more information.

		See Documentation/admin-guide/pm/sleep-states.rst for more

		information.



What:		/sys/power/mem_sleep

Date:		November 2016
@@ -35,7 +36,8 @@ Description: 
		represented by it to be used on subsequent attempts to suspend

		the system.



		See Documentation/power/states.txt for more information.

		See Documentation/admin-guide/pm/sleep-states.rst for more

		information.



What:		/sys/power/disk

Date:		September 2006

Documentation/admin-guide/README.rst

+1 −1
Original line number Diff line number Diff line
@@ -350,7 +350,7 @@ If something goes wrong 
   help debugging the problem.  The text above the dump is also

   important: it tells something about why the kernel dumped code (in

   the above example, it's due to a bad kernel pointer). More information

   on making sense of the dump is in Documentation/admin-guide/oops-tracing.rst

   on making sense of the dump is in Documentation/admin-guide/bug-hunting.rst



 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump

   as is, otherwise you will have to use the ``ksymoops`` program to make