Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Falcon <tlfalcon@linux.ibm.com>
To: netdev@vger.kernel.org
Cc: drt@linux.vnet.ibm.com, sukadev@linux.vnet.ibm.com,
	ljp@linux.vnet.ibm.com, cforno12@linux.ibm.com,
	Thomas Falcon <tlfalcon@linux.ibm.com>
Subject: [PATCH net-next 2/5] ibmvnic: Include documentation for ibmvnic sysfs files
Date: Mon, 31 Aug 2020 11:58:10 -0500	[thread overview]
Message-ID: <1598893093-14280-3-git-send-email-tlfalcon@linux.ibm.com> (raw)
In-Reply-To: <1598893093-14280-1-git-send-email-tlfalcon@linux.ibm.com>

Include documentation for existing ibmvnic sysfs files,
currently only for "failover," which is used to swap
the active hardware port to a backup port in redundant
backing hardware or failover configurations.

Signed-off-by: Thomas Falcon <tlfalcon@linux.ibm.com>
---
 Documentation/ABI/testing/sysfs-driver-ibmvnic | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 Documentation/ABI/testing/sysfs-driver-ibmvnic

diff --git a/Documentation/ABI/testing/sysfs-driver-ibmvnic b/Documentation/ABI/testing/sysfs-driver-ibmvnic
new file mode 100644
index 0000000..7fa2920
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-ibmvnic
@@ -0,0 +1,14 @@
+What:		/sys/devices/vio/<our device>/failover
+Date:		June 2017
+KernelVersion:	4.13
+Contact:	linuxppc-dev@lists.ozlabs.org
+Description:	If the ibmvnic device has been configured with redundant
+		physical NIC ports, the user may write "1" to the failover
+		file to trigger a device failover, which will reset the
+		ibmvnic device and swap to a backup physical port. If no
+		redundant physical port has been configured for the device,
+		the device will not reset and -EINVAL is returned. If anything
+		other than "1" is written to the file, -EINVAL will also be
+		returned.
+Users:		Any users of the ibmvnic driver which use redundant hardware
+		configurations.
-- 
1.8.3.1


  parent reply	other threads:[~2020-08-31 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 16:58 [PATCH net-next 0/5] ibmvnic: Report ACL settings in sysfs Thomas Falcon
2020-08-31 16:58 ` [PATCH net-next 1/5] ibmvnic: Create failover sysfs as part of an attribute group Thomas Falcon
2020-08-31 16:58 ` Thomas Falcon [this message]
2020-08-31 19:07   ` [PATCH net-next 2/5] ibmvnic: Include documentation for ibmvnic sysfs files Jakub Kicinski
2020-08-31 19:51     ` Thomas Falcon
2020-08-31 16:58 ` [PATCH net-next 3/5] ibmvnic: Remove ACL change indication definitions Thomas Falcon
2020-08-31 16:58 ` [PATCH net-next 4/5] ibmvnic: Reporting device ACL settings through sysfs Thomas Falcon
2020-09-02 21:51   ` Sukadev Bhattiprolu
2020-08-31 16:58 ` [PATCH net-next 5/5] ibmvnic: Provide documentation for ACL sysfs files Thomas Falcon
2020-08-31 19:26   ` Jakub Kicinski
2020-08-31 19:54     ` Thomas Falcon
2020-08-31 20:11       ` Jakub Kicinski
2020-08-31 21:44         ` Thomas Falcon
2020-08-31 22:00           ` Jakub Kicinski
2020-08-31 22:17             ` David Miller
2020-08-31 22:30               ` Thomas Falcon

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=1598893093-14280-3-git-send-email-tlfalcon@linux.ibm.com \
    --to=tlfalcon@linux.ibm.com \
    --cc=cforno12@linux.ibm.com \
    --cc=drt@linux.vnet.ibm.com \
    --cc=ljp@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sukadev@linux.vnet.ibm.com \
    --subject='Re: [PATCH net-next 2/5] ibmvnic: Include documentation for ibmvnic sysfs files' \
    /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

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).