From: Vadim Pasternak <vadimp@mellanox.com>
To: andy@infradead.org, dvhart@infradead.org
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vadim Pasternak <vadimp@mellanox.com>
Subject: [PATCH platform-next v2 02/10] Documentation/ABI: Fix documentation inconsistency for mlxreg-io sysfs interfaces
Date: Sun, 12 Jan 2020 12:18:41 +0000 [thread overview]
Message-ID: <20200112121849.7056-3-vadimp@mellanox.com> (raw)
In-Reply-To: <20200112121849.7056-1-vadimp@mellanox.com>
Fix attribute name from "jtag_enable", which described twice to
"cpld3_version", which is expected to be instead of second appearance
of "jtag_enable".
Fixes: 2752e34442b5 ("Documentation/ABI: Add new attribute for mlxreg-io sysfs interfaces")
Signed-off-by: Vadim Pasternak <vadimp@mellanox.com>
---
v1-v2:
Comments pointed out by Andy:
- Explain that patch fixes documentation inconsistency.
---
Documentation/ABI/stable/sysfs-driver-mlxreg-io | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/ABI/stable/sysfs-driver-mlxreg-io b/Documentation/ABI/stable/sysfs-driver-mlxreg-io
index 8ca498447aeb..8b1461fa3538 100644
--- a/Documentation/ABI/stable/sysfs-driver-mlxreg-io
+++ b/Documentation/ABI/stable/sysfs-driver-mlxreg-io
@@ -29,13 +29,13 @@ Description: This file shows the system fans direction:
The files are read only.
-What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/jtag_enable
+What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version
Date: November 2018
KernelVersion: 5.0
Contact: Vadim Pasternak <vadimpmellanox.com>
Description: These files show with which CPLD versions have been burned
- on LED board.
+ on LED or Gearbox board.
The files are read only.
--
2.11.0
next prev parent reply other threads:[~2020-01-12 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 12:18 [PATCH platform-next v2 00/10] platform/x86: Mellanox new system classes and new features Vadim Pasternak
2020-01-12 12:18 ` [PATCH platform-next v2 01/10] platform/x86: mlx-platform: Cosmetic changes Vadim Pasternak
2020-01-12 12:18 ` Vadim Pasternak [this message]
2020-01-12 12:18 ` [PATCH platform-next v2 03/10] Documentation/ABI: Add missed attribute for mlxreg-io sysfs interfaces Vadim Pasternak
2020-01-13 14:12 ` Andy Shevchenko
2020-01-12 12:18 ` [PATCH platform-next v2 04/10] platform/x86: mlx-platform: Add more definitions for system attributes Vadim Pasternak
2020-01-12 12:18 ` [PATCH platform-next v2 05/10] Documentation/ABI: Add new attribute for mlxreg-io sysfs interfaces Vadim Pasternak
2020-01-13 14:13 ` Andy Shevchenko
2020-01-12 12:18 ` [PATCH platform-next v2 06/10] platform/x86: mlx-platform: Set system mux configuration based on system type Vadim Pasternak
2020-01-12 12:18 ` [PATCH platform-next v2 07/10] platform/x86: mlx-platform: Add support for new " Vadim Pasternak
2020-01-12 12:18 ` [PATCH platform-next v2 08/10] platform/x86: mlx-platform: Add support for new capability register Vadim Pasternak
2020-01-12 12:18 ` [PATCH platform-next v2 09/10] platform/mellanox: mlxreg-hotplug: " Vadim Pasternak
2020-01-12 12:18 ` [PATCH platform-next v2 10/10] platform/x86: mlx-platform: Add support for next generation systems Vadim Pasternak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200112121849.7056-3-vadimp@mellanox.com \
--to=vadimp@mellanox.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).