Commit e529f4d6 authored by Peter Meerwald's avatar Peter Meerwald Committed by Johannes Berg

rfkill: Correctly document rkill subfolder range as >= 0 in sysfs-class-rfkill

The first subfolder is rfkill0, hence rfkillX (X >= 0).
Also fix two trivial typos.
Signed-off-by: default avatarPeter Meerwald-Stadler <pmeerw@pmeerw.net>
Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
parent b9771d41
...@@ -11,7 +11,7 @@ KernelVersion: v2.6.22 ...@@ -11,7 +11,7 @@ KernelVersion: v2.6.22
Contact: linux-wireless@vger.kernel.org, Contact: linux-wireless@vger.kernel.org,
Description: The rfkill class subsystem folder. Description: The rfkill class subsystem folder.
Each registered rfkill driver is represented by an rfkillX Each registered rfkill driver is represented by an rfkillX
subfolder (X being an integer > 0). subfolder (X being an integer >= 0).
What: /sys/class/rfkill/rfkill[0-9]+/name What: /sys/class/rfkill/rfkill[0-9]+/name
...@@ -48,8 +48,8 @@ Contact: linux-wireless@vger.kernel.org ...@@ -48,8 +48,8 @@ Contact: linux-wireless@vger.kernel.org
Description: Current state of the transmitter. Description: Current state of the transmitter.
This file was scheduled to be removed in 2014, but due to its This file was scheduled to be removed in 2014, but due to its
large number of users it will be sticking around for a bit large number of users it will be sticking around for a bit
longer. Despite it being marked as stabe, the newer "hard" and longer. Despite it being marked as stable, the newer "hard" and
"soft" interfaces should be preffered, since it is not possible "soft" interfaces should be preferred, since it is not possible
to express the 'soft and hard block' state of the rfkill driver to express the 'soft and hard block' state of the rfkill driver
through this interface. There will likely be another attempt to through this interface. There will likely be another attempt to
remove it in the future. remove it in the future.
......
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