public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>, Sean Paul <sean@poorly.run>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	dri-devel@lists.freedesktop.org
Subject: [PATCH] drm: Fix Kconfig indentation
Date: Wed, 20 Nov 2019 21:36:40 +0800	[thread overview]
Message-ID: <20191120133640.11659-1-krzk@kernel.org> (raw)

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>
---
 drivers/gpu/drm/Kconfig | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index 1168351267fd..ad1b6ecd2e08 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -94,18 +94,18 @@ config DRM_KMS_FB_HELPER
 	  FBDEV helpers for KMS drivers.
 
 config DRM_DEBUG_DP_MST_TOPOLOGY_REFS
-        bool "Enable refcount backtrace history in the DP MST helpers"
-        select STACKDEPOT
-        depends on DRM_KMS_HELPER
-        depends on DEBUG_KERNEL
-        depends on EXPERT
-        help
-          Enables debug tracing for topology refs in DRM's DP MST helpers. A
-          history of each topology reference/dereference will be printed to the
-          kernel log once a port or branch device's topology refcount reaches 0.
-
-          This has the potential to use a lot of memory and print some very
-          large kernel messages. If in doubt, say "N".
+	bool "Enable refcount backtrace history in the DP MST helpers"
+	select STACKDEPOT
+	depends on DRM_KMS_HELPER
+	depends on DEBUG_KERNEL
+	depends on EXPERT
+	help
+	  Enables debug tracing for topology refs in DRM's DP MST helpers. A
+	  history of each topology reference/dereference will be printed to the
+	  kernel log once a port or branch device's topology refcount reaches 0.
+
+	  This has the potential to use a lot of memory and print some very
+	  large kernel messages. If in doubt, say "N".
 
 config DRM_FBDEV_EMULATION
 	bool "Enable legacy fbdev support for your modesetting driver"
@@ -234,8 +234,8 @@ config DRM_RADEON
 	tristate "ATI Radeon"
 	depends on DRM && PCI && MMU
 	select FW_LOADER
-        select DRM_KMS_HELPER
-        select DRM_TTM
+	select DRM_KMS_HELPER
+	select DRM_TTM
 	select POWER_SUPPLY
 	select HWMON
 	select BACKLIGHT_CLASS_DEVICE
@@ -294,7 +294,7 @@ config DRM_VKMS
 	  If M is selected the module will be called vkms.
 
 config DRM_ATI_PCIGART
-        bool
+	bool
 
 source "drivers/gpu/drm/exynos/Kconfig"
 
-- 
2.17.1


             reply	other threads:[~2019-11-20 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 13:36 Krzysztof Kozlowski [this message]
2019-11-20 14:15 ` [PATCH] drm: Fix Kconfig indentation Jani Nikula

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191120133640.11659-1-krzk@kernel.org \
    --to=krzk@kernel.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=sean@poorly.run \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox