mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
synced 2026-04-23 05:56:14 -04:00
Merge tag 'docs-5.3' of git://git.lwn.net/linux
Pull Documentation updates from Jonathan Corbet:
"It's been a relatively busy cycle for docs:
- A fair pile of RST conversions, many from Mauro. These create more
than the usual number of simple but annoying merge conflicts with
other trees, unfortunately. He has a lot more of these waiting on
the wings that, I think, will go to you directly later on.
- A new document on how to use merges and rebases in kernel repos,
and one on Spectre vulnerabilities.
- Various improvements to the build system, including automatic
markup of function() references because some people, for reasons I
will never understand, were of the opinion that
:c:func:``function()`` is unattractive and not fun to type.
- We now recommend using sphinx 1.7, but still support back to 1.4.
- Lots of smaller improvements, warning fixes, typo fixes, etc"
* tag 'docs-5.3' of git://git.lwn.net/linux: (129 commits)
docs: automarkup.py: ignore exceptions when seeking for xrefs
docs: Move binderfs to admin-guide
Disable Sphinx SmartyPants in HTML output
doc: RCU callback locks need only _bh, not necessarily _irq
docs: format kernel-parameters -- as code
Doc : doc-guide : Fix a typo
platform: x86: get rid of a non-existent document
Add the RCU docs to the core-api manual
Documentation: RCU: Add TOC tree hooks
Documentation: RCU: Rename txt files to rst
Documentation: RCU: Convert RCU UP systems to reST
Documentation: RCU: Convert RCU linked list to reST
Documentation: RCU: Convert RCU basic concepts to reST
docs: filesystems: Remove uneeded .rst extension on toctables
scripts/sphinx-pre-install: fix out-of-tree build
docs: zh_CN: submitting-drivers.rst: Remove a duplicated Documentation/
Documentation: PGP: update for newer HW devices
Documentation: Add section about CPU vulnerabilities for Spectre
Documentation: platform: Delete x86-laptop-drivers.txt
docs: Note that :c:func: should no longer be used
...
This commit is contained in:
@@ -31,7 +31,7 @@ menuconfig FB
|
||||
in the /dev directory, i.e. /dev/fb*.
|
||||
|
||||
You need an utility program called fbset to make full use of frame
|
||||
buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
|
||||
buffer devices. Please read <file:Documentation/fb/framebuffer.rst>
|
||||
and the Framebuffer-HOWTO at
|
||||
<http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
|
||||
information.
|
||||
@@ -241,7 +241,7 @@ config FB_CIRRUS
|
||||
If you have a PCI-based system, this enables support for these
|
||||
chips: GD-543x, GD-544x, GD-5480.
|
||||
|
||||
Please read the file <file:Documentation/fb/cirrusfb.txt>.
|
||||
Please read the file <file:Documentation/fb/cirrusfb.rst>.
|
||||
|
||||
Say N unless you have such a graphics board or plan to get one
|
||||
before you next recompile the kernel.
|
||||
@@ -289,7 +289,7 @@ config FB_ARMCLCD
|
||||
|
||||
If you want to compile this as a module (=code which can be
|
||||
inserted into and removed from the running kernel), say M
|
||||
here and read <file:Documentation/kbuild/modules.txt>. The module
|
||||
here and read <file:Documentation/kbuild/modules.rst>. The module
|
||||
will be called amba-clcd.
|
||||
|
||||
config FB_ACORN
|
||||
@@ -615,7 +615,7 @@ config FB_UVESA
|
||||
|
||||
This driver generally provides more features than vesafb but
|
||||
requires a userspace helper application called 'v86d'. See
|
||||
<file:Documentation/fb/uvesafb.txt> for more information.
|
||||
<file:Documentation/fb/uvesafb.rst> for more information.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
@@ -630,7 +630,7 @@ config FB_VESA
|
||||
This is the frame buffer device driver for generic VESA 2.0
|
||||
compliant graphic cards. The older VESA 1.2 cards are not supported.
|
||||
You will get a boot time penguin logo at no additional cost. Please
|
||||
read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
|
||||
read <file:Documentation/fb/vesafb.rst>. If unsure, say Y.
|
||||
|
||||
config FB_EFI
|
||||
bool "EFI-based Framebuffer Support"
|
||||
@@ -828,7 +828,7 @@ config FB_PVR2
|
||||
module load time. The parameters look like "video=pvr2:XXX", where
|
||||
the meaning of XXX can be found at the end of the main source file
|
||||
(<file:drivers/video/pvr2fb.c>). Please see the file
|
||||
<file:Documentation/fb/pvr2fb.txt>.
|
||||
<file:Documentation/fb/pvr2fb.rst>.
|
||||
|
||||
config FB_OPENCORES
|
||||
tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
|
||||
@@ -991,7 +991,7 @@ config FB_I810
|
||||
module will be called i810fb.
|
||||
|
||||
For more information, please read
|
||||
<file:Documentation/fb/intel810.txt>
|
||||
<file:Documentation/fb/intel810.rst>
|
||||
|
||||
config FB_I810_GTF
|
||||
bool "use VESA Generalized Timing Formula"
|
||||
@@ -1061,7 +1061,7 @@ config FB_INTEL
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called intelfb.
|
||||
|
||||
For more information, please read <file:Documentation/fb/intelfb.txt>
|
||||
For more information, please read <file:Documentation/fb/intelfb.rst>
|
||||
|
||||
config FB_INTEL_DEBUG
|
||||
bool "Intel driver Debug Messages"
|
||||
@@ -1098,7 +1098,7 @@ config FB_MATROX
|
||||
|
||||
You can pass several parameters to the driver at boot time or at
|
||||
module load time. The parameters look like "video=matroxfb:XXX", and
|
||||
are described in <file:Documentation/fb/matroxfb.txt>.
|
||||
are described in <file:Documentation/fb/matroxfb.rst>.
|
||||
|
||||
config FB_MATROX_MILLENIUM
|
||||
bool "Millennium I/II support"
|
||||
@@ -1249,7 +1249,7 @@ config FB_ATY128
|
||||
help
|
||||
This driver supports graphics boards with the ATI Rage128 chips.
|
||||
Say Y if you have such a graphics board and read
|
||||
<file:Documentation/fb/aty128fb.txt>.
|
||||
<file:Documentation/fb/aty128fb.rst>.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called aty128fb.
|
||||
@@ -1511,7 +1511,7 @@ config FB_VOODOO1
|
||||
|
||||
WARNING: Do not use any application that uses the 3D engine
|
||||
(namely glide) while using this driver.
|
||||
Please read the <file:Documentation/fb/sstfb.txt> for supported
|
||||
Please read the <file:Documentation/fb/sstfb.rst> for supported
|
||||
options and other important info support.
|
||||
|
||||
config FB_VT8623
|
||||
@@ -1543,7 +1543,7 @@ config FB_TRIDENT
|
||||
There are also integrated versions of these chips called CyberXXXX,
|
||||
CyberImage or CyberBlade. These chips are mostly found in laptops
|
||||
but also on some motherboards including early VIA EPIA motherboards.
|
||||
For more information, read <file:Documentation/fb/tridentfb.txt>
|
||||
For more information, read <file:Documentation/fb/tridentfb.rst>
|
||||
|
||||
Say Y if you have such a graphics board.
|
||||
|
||||
@@ -1757,7 +1757,7 @@ config FB_PXA
|
||||
This driver is also available as a module ( = code which can be
|
||||
inserted and removed from the running kernel whenever you want). The
|
||||
module will be called pxafb. If you want to compile it as a module,
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
say M here and read <file:Documentation/kbuild/modules.rst>.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
@@ -1783,7 +1783,7 @@ config FB_PXA_PARAMETERS
|
||||
single model of flatpanel then you can safely leave this
|
||||
option disabled.
|
||||
|
||||
<file:Documentation/fb/pxafb.txt> describes the available parameters.
|
||||
<file:Documentation/fb/pxafb.rst> describes the available parameters.
|
||||
|
||||
config PXA3XX_GCU
|
||||
tristate "PXA3xx 2D graphics accelerator driver"
|
||||
@@ -1838,7 +1838,7 @@ config FB_W100
|
||||
This driver is also available as a module ( = code which can be
|
||||
inserted and removed from the running kernel whenever you want). The
|
||||
module will be called w100fb. If you want to compile it as a module,
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
say M here and read <file:Documentation/kbuild/modules.rst>.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
@@ -1867,7 +1867,7 @@ config FB_TMIO
|
||||
This driver is also available as a module ( = code which can be
|
||||
inserted and removed from the running kernel whenever you want). The
|
||||
module will be called tmiofb. If you want to compile it as a module,
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
say M here and read <file:Documentation/kbuild/modules.rst>.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
@@ -1914,7 +1914,7 @@ config FB_S3C2410
|
||||
This driver is also available as a module ( = code which can be
|
||||
inserted and removed from the running kernel whenever you want). The
|
||||
module will be called s3c2410fb. If you want to compile it as a module,
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
say M here and read <file:Documentation/kbuild/modules.rst>.
|
||||
|
||||
If unsure, say N.
|
||||
config FB_S3C2410_DEBUG
|
||||
@@ -1951,7 +1951,7 @@ config FB_SM501
|
||||
This driver is also available as a module ( = code which can be
|
||||
inserted and removed from the running kernel whenever you want). The
|
||||
module will be called sm501fb. If you want to compile it as a module,
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
say M here and read <file:Documentation/kbuild/modules.rst>.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
@@ -2284,7 +2284,7 @@ config FB_SM712
|
||||
|
||||
This driver is also available as a module. The module will be
|
||||
called sm712fb. If you want to compile it as a module, say M
|
||||
here and read <file:Documentation/kbuild/modules.txt>.
|
||||
here and read <file:Documentation/kbuild/modules.rst>.
|
||||
|
||||
source "drivers/video/fbdev/omap/Kconfig"
|
||||
source "drivers/video/fbdev/omap2/Kconfig"
|
||||
|
||||
Reference in New Issue
Block a user