[PATCH v3 6/6] Clarify how elements order list impacts priority

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This patch provides additional clarification and describes how
priority is determined according to the order.  Elements listed first
are given higher priority to those listed last.

Signed-off-by: Jorge Lopez <jorge.lopez2@xxxxxx>

---
Based on the latest platform-drivers-x86.git/for-next
---
 Documentation/ABI/testing/sysfs-class-firmware-attributes | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/Documentation/ABI/testing/sysfs-class-firmware-attributes b/Documentation/ABI/testing/sysfs-class-firmware-attributes
index d3830b8a398f..ed2ff3a74163 100644
--- a/Documentation/ABI/testing/sysfs-class-firmware-attributes
+++ b/Documentation/ABI/testing/sysfs-class-firmware-attributes
@@ -143,7 +143,11 @@ Description:
 		elements:
 					A file that can be read to obtain the possible
 					list of values of the <attr>. Values are separated using
-					semi-colon (``;``)
+					semi-colon (``;``). The order individual elements are listed
++					according to their priority.  An Element listed first has the
++					hightest priority. Writing the list in a different order to
++					current_value alters the priority order for the particular
++					attribute.
 
 		"sure-admin"-type specific properties:
 
@@ -384,7 +388,7 @@ Description:
 			==	=========================================
 			0	All BIOS attributes setting are current
 			1	A reboot is necessary to get pending BIOS
-			        attribute changes applied
+				attribute changes applied
 			==	=========================================
 
 		Note, userspace applications need to follow below steps for efficient
-- 
2.34.1




[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux