Date: Fri, 8 Apr 2011 14:18:54 +0000
In particular:
* The word `frame' was missing in `received frame',
so it has been added.
* The `RF' in `a RF' was both superfluous and awkward,
so it has been removed.
As for the rest of the changes, well, I just couldn't help myself!
Signed-off-by: Michael Witten <mfwit...@gmail.com>
---
drivers/net/wireless/ipw2x00/Kconfig | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/net/wireless/ipw2x00/Kconfig
b/drivers/net/wireless/ipw2x00/Kconfig
index 5397cd1..5abf297 100644
--- a/drivers/net/wireless/ipw2x00/Kconfig
+++ b/drivers/net/wireless/ipw2x00/Kconfig
@@ -112,13 +112,13 @@ config IPW2200_RADIOTAP
depends on IPW2200_MONITOR
config IPW2200_PROMISCUOUS
- bool "Enable creation of a RF radiotap promiscuous interface"
+ bool "Enable creation of a radiotap promiscuous interface"
depends on IPW2200_MONITOR
select IPW2200_RADIOTAP
---help---
- Enables the creation of a second interface prefixed 'rtap'.
- This second interface will provide every received in radiotap
- format.
+ Enables the creation of a second interface (the name of which
+ is prefixed with 'rtap'), which provides every received frame
+ in radiotap format.
This is useful for performing wireless network analysis while
maintaining an active association.
@@ -129,9 +129,9 @@ config IPW2200_PROMISCUOUS
% ifconfig rtap0 up
% tethereal -i rtap0
- If you do not specify 'rtap_iface=1' as a module parameter then
- the rtap interface will not be created and you will need to turn
- it on via sysfs:
+ If you do not specify 'rtap_iface=1' as a module parameter, then
+ the rtap interface will not be created automatically, but it can
+ still be created via sysfs:
% echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface
--
1.7.11.2.252.gc4a64c8
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
