usb: gadget: Fix Kconfig indentation

Adjust indentation from spaces to tab (+optional two spaces) as in
coding style with command like:
	$ sed -e 's/^        /\t/' -i */Kconfig

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Link: https://lore.kernel.org/r/20191121132905.29248-1-krzk@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/usb/gadget/legacy/Kconfig b/drivers/usb/gadget/legacy/Kconfig
index 38eaa94..119a4e4 100644 (file)
--- a/drivers/usb/gadget/legacy/Kconfig
+++ b/drivers/usb/gadget/legacy/Kconfig
@@ -149,21 +149,21 @@ config USB_ETH_RNDIS
           is given in comments found in that info file.
 
 config USB_ETH_EEM
-       bool "Ethernet Emulation Model (EEM) support"
-       depends on USB_ETH
+       bool "Ethernet Emulation Model (EEM) support"
+       depends on USB_ETH
        select USB_LIBCOMPOSITE
        select USB_F_EEM
-       help
-        CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
-        and therefore can be supported by more hardware.  Technically ECM and
-        EEM are designed for different applications.  The ECM model extends
-        the network interface to the target (e.g. a USB cable modem), and the
-        EEM model is for mobile devices to communicate with hosts using
-        ethernet over USB.  For Linux gadgets, however, the interface with
-        the host is the same (a usbX device), so the differences are minimal.
-
-        If you say "y" here, the Ethernet gadget driver will use the EEM
-        protocol rather than ECM.  If unsure, say "n".
+       help
+         CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
+         and therefore can be supported by more hardware.  Technically ECM and
+         EEM are designed for different applications.  The ECM model extends
+         the network interface to the target (e.g. a USB cable modem), and the
+         EEM model is for mobile devices to communicate with hosts using
+         ethernet over USB.  For Linux gadgets, however, the interface with
+         the host is the same (a usbX device), so the differences are minimal.
+
+         If you say "y" here, the Ethernet gadget driver will use the EEM
+         protocol rather than ECM.  If unsure, say "n".
 
 config USB_G_NCM
        tristate "Network Control Model (NCM) support"

diff --git a/drivers/usb/gadget/udc/Kconfig b/drivers/usb/gadget/udc/Kconfig
index acaec3a..ae70ce2 100644 (file)
--- a/drivers/usb/gadget/udc/Kconfig
+++ b/drivers/usb/gadget/udc/Kconfig
@@ -120,9 +120,9 @@ config USB_FOTG210_UDC
           dynamically linked module called "fotg210_udc".
 
 config USB_GR_UDC
-       tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
-       depends on HAS_DMA
-       help
+       tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
+       depends on HAS_DMA
+       help
          Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB
          VHDL IP core library.