Skip to content

Commit 5421cf8

Browse files
krzkdavem330
authored andcommitted
drivers: net: Fix Kconfig indentation, continued
Adjust indentation from spaces to tab (+optional two spaces) as in coding style. This fixes various indentation mixups (seven spaces, tab+one space, etc). Signed-off-by: Krzysztof Kozlowski <[email protected]> Signed-off-by: David S. Miller <[email protected]>
1 parent 1841b98 commit 5421cf8

File tree

10 files changed

+149
-149
lines changed

10 files changed

+149
-149
lines changed

drivers/net/Kconfig

Lines changed: 32 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -153,22 +153,22 @@ config IPVLAN_L3S
153153
select NET_L3_MASTER_DEV
154154

155155
config IPVLAN
156-
tristate "IP-VLAN support"
157-
depends on INET
158-
depends on IPV6 || !IPV6
159-
---help---
160-
This allows one to create virtual devices off of a main interface
161-
and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
162-
on packets. All interfaces (including the main interface) share L2
163-
making it transparent to the connected L2 switch.
156+
tristate "IP-VLAN support"
157+
depends on INET
158+
depends on IPV6 || !IPV6
159+
---help---
160+
This allows one to create virtual devices off of a main interface
161+
and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
162+
on packets. All interfaces (including the main interface) share L2
163+
making it transparent to the connected L2 switch.
164164

165-
Ipvlan devices can be added using the "ip" command from the
166-
iproute2 package starting with the iproute2-3.19 release:
165+
Ipvlan devices can be added using the "ip" command from the
166+
iproute2 package starting with the iproute2-3.19 release:
167167

168-
"ip link add link <main-dev> [ NAME ] type ipvlan"
168+
"ip link add link <main-dev> [ NAME ] type ipvlan"
169169

170-
To compile this driver as a module, choose M here: the module
171-
will be called ipvlan.
170+
To compile this driver as a module, choose M here: the module
171+
will be called ipvlan.
172172

173173
config IPVTAP
174174
tristate "IP-VLAN based tap driver"
@@ -185,11 +185,11 @@ config IPVTAP
185185
will be called ipvtap.
186186

187187
config VXLAN
188-
tristate "Virtual eXtensible Local Area Network (VXLAN)"
189-
depends on INET
190-
select NET_UDP_TUNNEL
191-
select GRO_CELLS
192-
---help---
188+
tristate "Virtual eXtensible Local Area Network (VXLAN)"
189+
depends on INET
190+
select NET_UDP_TUNNEL
191+
select GRO_CELLS
192+
---help---
193193
This allows one to create vxlan virtual interfaces that provide
194194
Layer 2 Networks over Layer 3 Networks. VXLAN is often used
195195
to tunnel virtual network infrastructure in virtualized environments.
@@ -200,12 +200,12 @@ config VXLAN
200200
will be called vxlan.
201201

202202
config GENEVE
203-
tristate "Generic Network Virtualization Encapsulation"
204-
depends on INET
205-
depends on IPV6 || !IPV6
206-
select NET_UDP_TUNNEL
207-
select GRO_CELLS
208-
---help---
203+
tristate "Generic Network Virtualization Encapsulation"
204+
depends on INET
205+
depends on IPV6 || !IPV6
206+
select NET_UDP_TUNNEL
207+
select GRO_CELLS
208+
---help---
209209
This allows one to create geneve virtual interfaces that provide
210210
Layer 2 Networks over Layer 3 Networks. GENEVE is often used
211211
to tunnel virtual network infrastructure in virtualized environments.
@@ -244,8 +244,8 @@ config MACSEC
244244
config NETCONSOLE
245245
tristate "Network console logging support"
246246
---help---
247-
If you want to log kernel messages over the network, enable this.
248-
See <file:Documentation/networking/netconsole.txt> for details.
247+
If you want to log kernel messages over the network, enable this.
248+
See <file:Documentation/networking/netconsole.txt> for details.
249249

250250
config NETCONSOLE_DYNAMIC
251251
bool "Dynamic reconfiguration of logging targets"
@@ -362,12 +362,12 @@ config NET_VRF
362362
support enables VRF devices.
363363

364364
config VSOCKMON
365-
tristate "Virtual vsock monitoring device"
366-
depends on VHOST_VSOCK
367-
---help---
368-
This option enables a monitoring net device for vsock sockets. It is
369-
mostly intended for developers or support to debug vsock issues. If
370-
unsure, say N.
365+
tristate "Virtual vsock monitoring device"
366+
depends on VHOST_VSOCK
367+
---help---
368+
This option enables a monitoring net device for vsock sockets. It is
369+
mostly intended for developers or support to debug vsock issues. If
370+
unsure, say N.
371371

372372
endif # NET_CORE
373373

drivers/net/caif/Kconfig

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -16,37 +16,37 @@ config CAIF_TTY
1616
depends on CAIF && TTY
1717
default n
1818
---help---
19-
The CAIF TTY transport driver is a Line Discipline (ldisc)
20-
identified as N_CAIF. When this ldisc is opened from user space
21-
it will redirect the TTY's traffic into the CAIF stack.
19+
The CAIF TTY transport driver is a Line Discipline (ldisc)
20+
identified as N_CAIF. When this ldisc is opened from user space
21+
it will redirect the TTY's traffic into the CAIF stack.
2222

2323
config CAIF_SPI_SLAVE
2424
tristate "CAIF SPI transport driver for slave interface"
2525
depends on CAIF && HAS_DMA
2626
default n
2727
---help---
28-
The CAIF Link layer SPI Protocol driver for Slave SPI interface.
29-
This driver implements a platform driver to accommodate for a
30-
platform specific SPI device. A sample CAIF SPI Platform device is
31-
provided in <file:Documentation/networking/caif/spi_porting.txt>.
28+
The CAIF Link layer SPI Protocol driver for Slave SPI interface.
29+
This driver implements a platform driver to accommodate for a
30+
platform specific SPI device. A sample CAIF SPI Platform device is
31+
provided in <file:Documentation/networking/caif/spi_porting.txt>.
3232

3333
config CAIF_SPI_SYNC
3434
bool "Next command and length in start of frame"
3535
depends on CAIF_SPI_SLAVE
3636
default n
3737
---help---
38-
Putting the next command and length in the start of the frame can
39-
help to synchronize to the next transfer in case of over or under-runs.
40-
This option also needs to be enabled on the modem.
38+
Putting the next command and length in the start of the frame can
39+
help to synchronize to the next transfer in case of over or under-runs.
40+
This option also needs to be enabled on the modem.
4141

4242
config CAIF_HSI
43-
tristate "CAIF HSI transport driver"
44-
depends on CAIF
45-
default n
46-
---help---
47-
The CAIF low level driver for CAIF over HSI.
48-
Be aware that if you enable this then you also need to
49-
enable a low-level HSI driver.
43+
tristate "CAIF HSI transport driver"
44+
depends on CAIF
45+
default n
46+
---help---
47+
The CAIF low level driver for CAIF over HSI.
48+
Be aware that if you enable this then you also need to
49+
enable a low-level HSI driver.
5050

5151
config CAIF_VIRTIO
5252
tristate "CAIF virtio transport driver"
@@ -56,7 +56,7 @@ config CAIF_VIRTIO
5656
select GENERIC_ALLOCATOR
5757
default n
5858
---help---
59-
The CAIF driver for CAIF over Virtio.
59+
The CAIF driver for CAIF over Virtio.
6060

6161
if CAIF_VIRTIO
6262
source "drivers/vhost/Kconfig.vringh"

drivers/net/ethernet/freescale/fs_enet/Kconfig

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
# SPDX-License-Identifier: GPL-2.0-only
22
config FS_ENET
3-
tristate "Freescale Ethernet Driver"
4-
depends on NET_VENDOR_FREESCALE && (CPM1 || CPM2 || PPC_MPC512x)
5-
select MII
6-
select PHYLIB
3+
tristate "Freescale Ethernet Driver"
4+
depends on NET_VENDOR_FREESCALE && (CPM1 || CPM2 || PPC_MPC512x)
5+
select MII
6+
select PHYLIB
77

88
config FS_ENET_MPC5121_FEC
99
def_bool y if (FS_ENET && PPC_MPC512x)

drivers/net/ieee802154/Kconfig

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,9 +74,9 @@ config IEEE802154_ATUSB
7474
The module will be called 'atusb'.
7575

7676
config IEEE802154_ADF7242
77-
tristate "ADF7242 transceiver driver"
78-
depends on IEEE802154_DRIVERS && MAC802154
79-
depends on SPI
77+
tristate "ADF7242 transceiver driver"
78+
depends on IEEE802154_DRIVERS && MAC802154
79+
depends on SPI
8080
---help---
8181
Say Y here to enable the ADF7242 SPI 802.15.4 wireless
8282
controller.
@@ -107,9 +107,9 @@ config IEEE802154_CA8210_DEBUGFS
107107
management entities.
108108

109109
config IEEE802154_MCR20A
110-
tristate "MCR20A transceiver driver"
111-
depends on IEEE802154_DRIVERS && MAC802154
112-
depends on SPI
110+
tristate "MCR20A transceiver driver"
111+
depends on IEEE802154_DRIVERS && MAC802154
112+
depends on SPI
113113
---help---
114114
Say Y here to enable the MCR20A SPI 802.15.4 wireless
115115
controller.

drivers/net/wireless/ath/Kconfig

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,12 +30,12 @@ config ATH_DEBUG
3030
Right now only ath9k makes use of this.
3131

3232
config ATH_TRACEPOINTS
33-
bool "Atheros wireless tracing"
34-
depends on ATH_DEBUG
35-
depends on EVENT_TRACING
36-
---help---
37-
This option enables tracepoints for atheros wireless drivers.
38-
Currently, ath9k makes use of this facility.
33+
bool "Atheros wireless tracing"
34+
depends on ATH_DEBUG
35+
depends on EVENT_TRACING
36+
---help---
37+
This option enables tracepoints for atheros wireless drivers.
38+
Currently, ath9k makes use of this facility.
3939

4040
config ATH_REG_DYNAMIC_USER_REG_HINTS
4141
bool "Atheros dynamic user regulatory hints"
Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
# SPDX-License-Identifier: ISC
22
config AR5523
3-
tristate "Atheros AR5523 wireless driver support"
4-
depends on MAC80211 && USB
5-
select ATH_COMMON
6-
select FW_LOADER
7-
---help---
8-
This module add support for AR5523 based USB dongles such as D-Link
9-
DWL-G132, Netgear WPN111 and many more.
3+
tristate "Atheros AR5523 wireless driver support"
4+
depends on MAC80211 && USB
5+
select ATH_COMMON
6+
select FW_LOADER
7+
---help---
8+
This module add support for AR5523 based USB dongles such as D-Link
9+
DWL-G132, Netgear WPN111 and many more.

drivers/net/wireless/ath/ath9k/Kconfig

Lines changed: 29 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -144,13 +144,13 @@ config ATH9K_RFKILL
144144
a platform that can toggle the RF-Kill GPIO.
145145

146146
config ATH9K_CHANNEL_CONTEXT
147-
bool "Channel Context support"
148-
depends on ATH9K
149-
default n
150-
---help---
151-
This option enables channel context support in ath9k, which is needed
152-
for multi-channel concurrency. Enable this if P2P PowerSave support
153-
is required.
147+
bool "Channel Context support"
148+
depends on ATH9K
149+
default n
150+
---help---
151+
This option enables channel context support in ath9k, which is needed
152+
for multi-channel concurrency. Enable this if P2P PowerSave support
153+
is required.
154154

155155
config ATH9K_PCOEM
156156
bool "Atheros ath9k support for PC OEM cards" if EXPERT
@@ -162,32 +162,32 @@ config ATH9K_PCI_NO_EEPROM
162162
depends on ATH9K_PCI
163163
default n
164164
help
165-
This separate driver provides a loader in order to support the
166-
AR500X to AR92XX-generation of ath9k PCI(e) WiFi chips, which have
167-
their initialization data (which contains the real PCI Device ID
168-
that ath9k will need) stored together with the calibration data out
169-
of reach for the ath9k chip.
165+
This separate driver provides a loader in order to support the
166+
AR500X to AR92XX-generation of ath9k PCI(e) WiFi chips, which have
167+
their initialization data (which contains the real PCI Device ID
168+
that ath9k will need) stored together with the calibration data out
169+
of reach for the ath9k chip.
170170

171-
These devices are usually various network appliances, routers or
172-
access Points and such.
171+
These devices are usually various network appliances, routers or
172+
access Points and such.
173173

174-
If unsure say N.
174+
If unsure say N.
175175

176176
config ATH9K_HTC
177-
tristate "Atheros HTC based wireless cards support"
178-
depends on USB && MAC80211
179-
select ATH9K_HW
180-
select MAC80211_LEDS
181-
select LEDS_CLASS
182-
select NEW_LEDS
183-
select ATH9K_COMMON
184-
---help---
185-
Support for Atheros HTC based cards.
186-
Chipsets supported: AR9271
187-
188-
For more information: http://wireless.kernel.org/en/users/Drivers/ath9k_htc
189-
190-
The built module will be ath9k_htc.
177+
tristate "Atheros HTC based wireless cards support"
178+
depends on USB && MAC80211
179+
select ATH9K_HW
180+
select MAC80211_LEDS
181+
select LEDS_CLASS
182+
select NEW_LEDS
183+
select ATH9K_COMMON
184+
---help---
185+
Support for Atheros HTC based cards.
186+
Chipsets supported: AR9271
187+
188+
For more information: http://wireless.kernel.org/en/users/Drivers/ath9k_htc
189+
190+
The built module will be ath9k_htc.
191191

192192
config ATH9K_HTC_DEBUGFS
193193
bool "Atheros ath9k_htc debugging"

drivers/net/wireless/atmel/Kconfig

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -13,29 +13,29 @@ config WLAN_VENDOR_ATMEL
1313
if WLAN_VENDOR_ATMEL
1414

1515
config ATMEL
16-
tristate "Atmel at76c50x chipset 802.11b support"
17-
depends on CFG80211 && (PCI || PCMCIA)
18-
select WIRELESS_EXT
19-
select WEXT_PRIV
20-
select FW_LOADER
21-
select CRC32
22-
---help---
23-
A driver 802.11b wireless cards based on the Atmel fast-vnet
24-
chips. This driver supports standard Linux wireless extensions.
25-
26-
Many cards based on this chipset do not have flash memory
27-
and need their firmware loaded at start-up. If yours is
28-
one of these, you will need to provide a firmware image
29-
to be loaded into the card by the driver. The Atmel
30-
firmware package can be downloaded from
31-
<http://www.thekelleys.org.uk/atmel>
16+
tristate "Atmel at76c50x chipset 802.11b support"
17+
depends on CFG80211 && (PCI || PCMCIA)
18+
select WIRELESS_EXT
19+
select WEXT_PRIV
20+
select FW_LOADER
21+
select CRC32
22+
---help---
23+
A driver 802.11b wireless cards based on the Atmel fast-vnet
24+
chips. This driver supports standard Linux wireless extensions.
25+
26+
Many cards based on this chipset do not have flash memory
27+
and need their firmware loaded at start-up. If yours is
28+
one of these, you will need to provide a firmware image
29+
to be loaded into the card by the driver. The Atmel
30+
firmware package can be downloaded from
31+
<http://www.thekelleys.org.uk/atmel>
3232

3333
config PCI_ATMEL
34-
tristate "Atmel at76c506 PCI cards"
35-
depends on ATMEL && PCI
36-
---help---
37-
Enable support for PCI and mini-PCI cards containing the
38-
Atmel at76c506 chip.
34+
tristate "Atmel at76c506 PCI cards"
35+
depends on ATMEL && PCI
36+
---help---
37+
Enable support for PCI and mini-PCI cards containing the
38+
Atmel at76c506 chip.
3939

4040
config PCMCIA_ATMEL
4141
tristate "Atmel at76c502/at76c504 PCMCIA cards"

0 commit comments

Comments
 (0)