From: Daniel Vetter <daniel@ffwll.ch>
To: Colin King <colin.king@canonical.com>
Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/gma500: clean up indentation issues
Date: Tue, 22 Sep 2020 15:19:16 +0200 [thread overview]
Message-ID: <20200922131916.GM438822@phenom.ffwll.local> (raw)
In-Reply-To: <20200920141407.32672-1-colin.king@canonical.com>
On Sun, Sep 20, 2020 at 03:14:07PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are a couple of statements that are indented too deeply,
> remove the extraneous tabs and also an empty line.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Pushed to drm-misc-next, thanks for your patch.
-Daniel
> ---
> drivers/gpu/drm/gma500/cdv_intel_dp.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/gma500/cdv_intel_dp.c b/drivers/gpu/drm/gma500/cdv_intel_dp.c
> index 720a767118c9..50016a754172 100644
> --- a/drivers/gpu/drm/gma500/cdv_intel_dp.c
> +++ b/drivers/gpu/drm/gma500/cdv_intel_dp.c
> @@ -1501,8 +1501,7 @@ cdv_intel_dp_start_link_train(struct gma_encoder *encoder)
> clock_recovery = false;
>
> DRM_DEBUG_KMS("Start train\n");
> - reg = DP | DP_LINK_TRAIN_PAT_1;
> -
> + reg = DP | DP_LINK_TRAIN_PAT_1;
>
> for (;;) {
> /* Use intel_dp->train_set[0] to set the voltage and pre emphasis values */
> @@ -1575,7 +1574,7 @@ cdv_intel_dp_complete_link_train(struct gma_encoder *encoder)
> cr_tries = 0;
>
> DRM_DEBUG_KMS("\n");
> - reg = DP | DP_LINK_TRAIN_PAT_2;
> + reg = DP | DP_LINK_TRAIN_PAT_2;
>
> for (;;) {
>
> --
> 2.27.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2020-09-22 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 14:14 Colin King
2020-09-22 13:19 ` Daniel Vetter [this message]
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=20200922131916.GM438822@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=colin.king@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.com \
/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
all inboxes | Powered by JetHome®