On Sun, Jan 13, 2019 at 6:32 AM Darren Hart (VMware)
wrote:
>
> The mlxreg-io for the merge window assumed 4.21 as the next kernel
> version. Replace 4.21 with 5.0.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Darren Hart (VMware)
> ---
> Documentation/ABI/stable/sysfs-driver-mlxreg-io | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/ABI/stable/sysfs-driver-mlxreg-io
> b/Documentation/ABI/stable/sysfs-driver-mlxreg-io
> index 9b642669cb16..169fe08a649b 100644
> --- a/Documentation/ABI/stable/sysfs-driver-mlxreg-io
> +++ b/Documentation/ABI/stable/sysfs-driver-mlxreg-io
> @@ -24,7 +24,7 @@ What:
> /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/
> cpld3_version
>
> Date: November 2018
> -KernelVersion: 4.21
> +KernelVersion: 5.0
> Contact: Vadim Pasternak
> Description: These files show with which CPLD versions have been burned
> on LED board.
> @@ -35,7 +35,7 @@ What:
> /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/
> jtag_enable
>
> Date: November 2018
> -KernelVersion: 4.21
> +KernelVersion: 5.0
> Contact: Vadim Pasternak
> Description: These files enable and disable the access to the JTAG domain.
> By default access to the JTAG domain is disabled.
> @@ -105,7 +105,7 @@ What:
> /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/
> reset_voltmon_upgrade_fail
>
> Date: November 2018
> -KernelVersion: 4.21
> +KernelVersion: 5.0
> Contact: Vadim Pasternak
> Description: These files show the system reset cause, as following: ComEx
> power fail, reset from ComEx, system platform reset, reset
> --
> 2.17.2
>
>
> --
> Darren Hart
> VMware Open Source Technology Center
--
With Best Regards,
Andy Shevchenko
