media: staging: use tabs instead of spaces at Kconfig and davinci

Even on text and Kconfigs, what we do on media is to use
tabs for indentation.

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>

diff --git a/drivers/staging/media/Kconfig b/drivers/staging/media/Kconfig
index 227437f22acfc49c23134c8e0079460f201e7548..e68e1d343d53ba11d266af71a32e1e9569e2cc7a 100644 (file)
--- a/drivers/staging/media/Kconfig
+++ b/drivers/staging/media/Kconfig
@@ -1,19 +1,19 @@
 menuconfig STAGING_MEDIA
-        bool "Media staging drivers"
-        default n
-        ---help---
-          This option allows you to select a number of media drivers that
+       bool "Media staging drivers"
+       default n
+       ---help---
+         This option allows you to select a number of media drivers that
          don't have the "normal" Linux kernel quality level.
          Most of them don't follow properly the V4L, DVB and/or RC API's,
          so, they won't likely work fine with the existing applications.
          That also means that, once fixed, their API's will change to match
          the existing ones.
 
-          If you wish to work on these drivers, to help improve them, or
-          to report problems you have with them, please use the
+         If you wish to work on these drivers, to help improve them, or
+         to report problems you have with them, please use the
          linux-media@vger.kernel.org mailing list.
 
-          If in doubt, say N here.
+         If in doubt, say N here.
 
 
 if STAGING_MEDIA && MEDIA_SUPPORT

diff --git a/drivers/staging/media/davinci_vpfe/TODO b/drivers/staging/media/davinci_vpfe/TODO
index 7015ab35ded57cac379468e145ce7890eefe3d3b..3e5477e8cfa5effe4466f37117ed24298e97cc01 100644 (file)
--- a/drivers/staging/media/davinci_vpfe/TODO
+++ b/drivers/staging/media/davinci_vpfe/TODO
@@ -2,11 +2,11 @@ TODO (general):
 ==================================
 
 - User space interface refinement
-        - Controls should be used when possible rather than private ioctl
-        - No enums should be used
-        - Use of MC and V4L2 subdev APIs when applicable
-        - Single interface header might suffice
-        - Current interface forces to configure everything at once
+       - Controls should be used when possible rather than private ioctl
+       - No enums should be used
+       - Use of MC and V4L2 subdev APIs when applicable
+       - Single interface header might suffice
+       - Current interface forces to configure everything at once
 - Get rid of the dm365_ipipe_hw.[ch] layer
 - Active external sub-devices defined by link configuration; no strcmp
   needed