From: Jani Nikula <jani.nikula@linux.intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, linux-kernel@vger.kernel.org
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH] drm/vc4: Fix Kconfig indentation
Date: Wed, 27 Nov 2019 15:13:47 +0200 [thread overview]
Message-ID: <87k17lo41g.fsf@intel.com> (raw)
In-Reply-To: <20191121132919.29430-1-krzk@kernel.org>
On Thu, 21 Nov 2019, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> Adjust indentation from spaces to tab (+optional two spaces) as in
> coding style with command like:
> $ sed -e 's/^ /\t/' -i */Kconfig
Btw have you updated checkpatch.pl to try to keep the Kconfigs from
bitrotting back to having different indentation? Or the config tools?
BR,
Jani.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> drivers/gpu/drm/vc4/Kconfig | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/vc4/Kconfig b/drivers/gpu/drm/vc4/Kconfig
> index 7c2317efd5b7..118e8a426b1a 100644
> --- a/drivers/gpu/drm/vc4/Kconfig
> +++ b/drivers/gpu/drm/vc4/Kconfig
> @@ -22,9 +22,9 @@ config DRM_VC4
> our display setup.
>
> config DRM_VC4_HDMI_CEC
> - bool "Broadcom VC4 HDMI CEC Support"
> - depends on DRM_VC4
> - select CEC_CORE
> - help
> + bool "Broadcom VC4 HDMI CEC Support"
> + depends on DRM_VC4
> + select CEC_CORE
> + help
> Choose this option if you have a Broadcom VC4 GPU
> and want to use CEC.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-11-27 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 13:29 [PATCH] drm/vc4: Fix Kconfig indentation Krzysztof Kozlowski
2019-11-25 9:04 ` Daniel Vetter
2019-11-27 13:13 ` Jani Nikula [this message]
2019-11-28 2:01 ` Krzysztof Kozlowski
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=87k17lo41g.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).