rtl8211F_led_control

hc

2024-05-11 297b60346df8beafee954a0fd7c2d64f33f3b9bc

 kernel/drivers/net/arcnet/Kconfig
..
..
@@ -1,3 +1,4 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
1
2
 #
2
3
 # Arcnet configuration
3
4
 #
..
..
@@ -5,10 +6,10 @@
5
6
 menuconfig ARCNET
6
7
 	depends on NETDEVICES && (ISA || PCI || PCMCIA)
7
8
 	tristate "ARCnet support"
8
-	---help---
9
+	help
9
10
 	  If you have a network card of this type, say Y and check out the
10
11
 	  (arguably) beautiful poetry in
11
-	  <file:Documentation/networking/arcnet.txt>.
12
+	  <file:Documentation/networking/arcnet.rst>.
12
13
 
13
14
 	  You need both this driver, and the driver for the particular ARCnet
14
15
 	  chipset of your card. If you don't know, then it's probably a
..
..
@@ -27,12 +28,12 @@
27
28
 	  arc0 device.  You need to say Y here to communicate with
28
29
 	  industry-standard RFC1201 implementations, like the arcether.com
29
30
 	  packet driver or most DOS/Windows ODI drivers.  Please read the
30
-	  ARCnet documentation in <file:Documentation/networking/arcnet.txt>
31
+	  ARCnet documentation in <file:Documentation/networking/arcnet.rst>
31
32
 	  for more information about using arc0.
32
33
 
33
34
 config ARCNET_1051
34
35
 	tristate "Enable old ARCNet packet format (RFC 1051)"
35
-	---help---
36
+	help
36
37
 	  This allows you to use RFC1051 with your ARCnet card via the virtual
37
38
 	  arc0s device. You only need arc0s if you want to talk to ARCnet
38
39
 	  software complying with the "old" standard, specifically, the DOS
..
..
@@ -41,7 +42,7 @@
41
42
 	  industry-standard RFC1201 implementations, like the arcether.com
42
43
 	  packet driver or most DOS/Windows ODI drivers. RFC1201 is included
43
44
 	  automatically as the arc0 device. Please read the ARCnet
44
-	  documentation in <file:Documentation/networking/arcnet.txt> for more
45
+	  documentation in <file:Documentation/networking/arcnet.rst> for more
45
46
 	  information about using arc0e and arc0s.
46
47
 
47
48
 config ARCNET_RAW
..
..
@@ -55,19 +56,19 @@
55
56
 	tristate "Enable CAP mode packet interface"
56
57
 	help
57
58
 	  ARCnet "cap mode" packet encapsulation. Used to get the hardware
58
-          acknowledge back to userspace. After the initial protocol byte every
59
-          packet is stuffed with an extra 4 byte "cookie" which doesn't
60
-          actually appear on the network. After transmit the driver will send
61
-          back a packet with protocol byte 0 containing the status of the
62
-          transmission:
63
-             0=no hardware acknowledge
64
-             1=excessive nak
65
-             2=transmission accepted by the receiver hardware
59
+	  acknowledge back to userspace. After the initial protocol byte every
60
+	  packet is stuffed with an extra 4 byte "cookie" which doesn't
61
+	  actually appear on the network. After transmit the driver will send
62
+	  back a packet with protocol byte 0 containing the status of the
63
+	  transmission:
64
+	     0=no hardware acknowledge
65
+	     1=excessive nak
66
+	     2=transmission accepted by the receiver hardware
66
67
 
67
-          Received packets are also stuffed with the extra 4 bytes but it will
68
-          be random data.
68
+	  Received packets are also stuffed with the extra 4 bytes but it will
69
+	  be random data.
69
70
 
70
-          Cap only listens to protocol 1-8.
71
+	  Cap only listens to protocol 1-8.
71
72
 
72
73
 config ARCNET_COM90xx
73
74
 	tristate "ARCnet COM90xx (normal) chipset driver"
..
..
@@ -81,7 +82,7 @@
81
82
 
82
83
 config ARCNET_COM90xxIO
83
84
 	tristate "ARCnet COM90xx (IO mapped) chipset driver"
84
-	---help---
85
+	help
85
86
 	  This is the chipset driver for the COM90xx cards, using them in
86
87
 	  IO-mapped mode instead of memory-mapped mode. This is slower than
87
88
 	  the normal driver. Only use it if your card doesn't support shared
..
..
@@ -92,7 +93,7 @@
92
93
 
93
94
 config ARCNET_RIM_I
94
95
 	tristate "ARCnet COM90xx (RIM I) chipset driver"
95
-	---help---
96
+	help
96
97
 	  This is yet another chipset driver for the COM90xx cards, but this
97
98
 	  time only using memory-mapped mode, and no IO ports at all. This
98
99
 	  driver is completely untested, so if you have one of these cards,