Commit 164e3271 authored by Jonathan Corbet's avatar Jonathan Corbet Committed by Hans de Goede

docs: ABI: fix documentation warning in sysfs-driver-mlxreg-io

The use of a Sphinx list within this ABI file caused the following warning:

  Documentation/ABI/stable/sysfs-driver-mlxreg-io:230: WARNING: Unexpected indentation.
  Documentation/ABI/stable/sysfs-driver-mlxreg-io:230: WARNING: Block quote ends without a blank line; unexpected unindent.

Remove the bullets to make the warning go away and get proper formatting.
Reported-by: default avatarStephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
parent b8d4d350
...@@ -231,16 +231,19 @@ Date: October 2021 ...@@ -231,16 +231,19 @@ Date: October 2021
KernelVersion: 5.16 KernelVersion: 5.16
Contact: Vadim Pasternak <vadimp@nvidia.com> Contact: Vadim Pasternak <vadimp@nvidia.com>
Description: The files represent BIOS statuses: Description: The files represent BIOS statuses:
- bios_active_image: location of current active BIOS image:
0: Top, 1: Bottom. bios_active_image: location of current active BIOS image:
The reported value should correspond to value expected by OS 0: Top, 1: Bottom.
in case of BIOS safe mode is 0. This bit is related to Intel The reported value should correspond to value expected by OS
top-swap feature of DualBios on the same flash. in case of BIOS safe mode is 0. This bit is related to Intel
- bios_auth_fail: BIOS upgrade is failed because provided BIOS top-swap feature of DualBios on the same flash.
image is not signed correctly.
- bios_upgrade_fail: BIOS upgrade is failed by some other bios_auth_fail: BIOS upgrade is failed because provided BIOS
reason not because authentication. For example due to image is not signed correctly.
physical SPI flash problem.
bios_upgrade_fail: BIOS upgrade is failed by some other
reason not because authentication. For example due to
physical SPI flash problem.
The files are read only. The files are read only.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment