docs: don't use nested tables

Nested tables aren't supported for pdf output on Sphinx 1.7.9:

	admin-guide/laptops/sonypi:: nested tables are not yet implemented.
	admin-guide/laptops/toshiba_haps:: nested tables are not yet implemented.
	driver-api/nvdimm/btt:: nested tables are not yet implemented.
	s390/debugging390:: nested tables are not yet implemented.

Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Acked-by: Andy Shevchenko <andy.shevchenko@gmail.com> # laptops
This commit is contained in:
Mauro Carvalho Chehab
2019-07-06 13:38:56 -03:00
parent c2746a1eb7
commit eddeed127b
4 changed files with 18 additions and 20 deletions

View File

@@ -89,9 +89,8 @@ statically linked into the kernel). Those options are:
set to 0xffffffff, meaning that all possible events set to 0xffffffff, meaning that all possible events
will be tried. You can use the following bits to will be tried. You can use the following bits to
construct your own event mask (from construct your own event mask (from
drivers/char/sonypi.h): drivers/char/sonypi.h)::
======================== ======
SONYPI_JOGGER_MASK 0x0001 SONYPI_JOGGER_MASK 0x0001
SONYPI_CAPTURE_MASK 0x0002 SONYPI_CAPTURE_MASK 0x0002
SONYPI_FNKEY_MASK 0x0004 SONYPI_FNKEY_MASK 0x0004
@@ -106,7 +105,6 @@ statically linked into the kernel). Those options are:
SONYPI_MEMORYSTICK_MASK 0x0800 SONYPI_MEMORYSTICK_MASK 0x0800
SONYPI_BATTERY_MASK 0x1000 SONYPI_BATTERY_MASK 0x1000
SONYPI_WIRELESS_MASK 0x2000 SONYPI_WIRELESS_MASK 0x2000
======================== ======
useinput: if set (which is the default) two input devices are useinput: if set (which is the default) two input devices are
created, one which interprets the jogdial events as created, one which interprets the jogdial events as

View File

@@ -75,7 +75,7 @@ The sysfs files under /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/ are:
protection_level The protection_level is readable and writeable, and protection_level The protection_level is readable and writeable, and
provides a way to let userspace query the current protection provides a way to let userspace query the current protection
level, as well as set the desired protection level, the level, as well as set the desired protection level, the
available protection levels are: available protection levels are::
============ ======= ========== ======== ============ ======= ========== ========
0 - Disabled 1 - Low 2 - Medium 3 - High 0 - Disabled 1 - Low 2 - Medium 3 - High

View File

@@ -83,7 +83,7 @@ flags, and the remaining form the internal block number.
======== ============================================================= ======== =============================================================
Bit Description Bit Description
======== ============================================================= ======== =============================================================
31 - 30 Error and Zero flags - Used in the following way: 31 - 30 Error and Zero flags - Used in the following way::
== == ==================================================== == == ====================================================
31 30 Description 31 30 Description

View File

@@ -170,7 +170,7 @@ currently running at.
| +----------------+-------------------------------------------------+ | +----------------+-------------------------------------------------+
| | 32 | Basic Addressing Mode | | | 32 | Basic Addressing Mode |
| | | | | | | |
| | | Used to set addressing mode | | | | Used to set addressing mode:: |
| | | | | | | |
| | | +---------+----------+----------+ | | | | +---------+----------+----------+ |
| | | | PSW 31 | PSW 32 | | | | | | | PSW 31 | PSW 32 | | |