public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Robert Foss <rfoss@kernel.org>, Yang Li <yang.lee@linux.alibaba.com>
Cc: neil.armstrong@linaro.org, jonas@kwiboo.se,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	jernej.skrabec@gmail.com, Laurent.pinchart@ideasonboard.com,
	andrzej.hajda@intel.com
Subject: Re: [PATCH -next] drm/bridge: clean up some inconsistent indentings
Date: Mon, 25 Sep 2023 14:08:25 +0300	[thread overview]
Message-ID: <87a5tao6hi.fsf@intel.com> (raw)
In-Reply-To: <CAN6tsi44s3h3Ox3mK2pi+Mw8pGCB9fgMcoWmJhCenHoK9=t=-w@mail.gmail.com>

On Mon, 25 Sep 2023, Robert Foss <rfoss@kernel.org> wrote:
> NAK

Feels a bit harsh.

> Personally I value maintaining a simple to follow `git blame` history
> over correcting indentation.
>
> Ideally bad indentation should never be committed in the first place.

Agreed, but when that inevitably happens, do you really want it to be
cast in stone? To me leaving bad indent (or style, or whatever) in place
indicates we don't care, while the opposite is true.

Maybe look into tooling that lets you easily git blame the parent commit
of a line in git blame? (For example, in emacs vc-annotate, it's just a
matter of hitting 'a'.)


BR,
Jani.


>
> On Wed, Sep 20, 2023 at 2:44 AM Yang Li <yang.lee@linux.alibaba.com> wrote:
>>
>> drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c:336 dw_hdmi_cec_suspend() warn: inconsistent indenting
>>
>> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
>> ---
>>  drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c
>> index 673661160e54..fe2ff4984fc5 100644
>> --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c
>> +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c
>> @@ -333,9 +333,9 @@ static int __maybe_unused dw_hdmi_cec_suspend(struct device *dev)
>>         struct dw_hdmi_cec *cec = dev_get_drvdata(dev);
>>
>>         /* store interrupt status/mask registers */
>> -        cec->regs_polarity = dw_hdmi_read(cec, HDMI_CEC_POLARITY);
>> -        cec->regs_mask = dw_hdmi_read(cec, HDMI_CEC_MASK);
>> -        cec->regs_mute_stat0 = dw_hdmi_read(cec, HDMI_IH_MUTE_CEC_STAT0);
>> +       cec->regs_polarity = dw_hdmi_read(cec, HDMI_CEC_POLARITY);
>> +       cec->regs_mask = dw_hdmi_read(cec, HDMI_CEC_MASK);
>> +       cec->regs_mute_stat0 = dw_hdmi_read(cec, HDMI_IH_MUTE_CEC_STAT0);
>>
>>         return 0;
>>  }
>> --
>> 2.20.1.7.g153144c
>>

-- 
Jani Nikula, Intel

      reply	other threads:[~2023-09-25 11:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  0:44 [PATCH -next] drm/bridge: clean up some inconsistent indentings Yang Li
2023-09-25 10:50 ` Robert Foss
2023-09-25 11:08   ` Jani Nikula [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=87a5tao6hi.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=andrzej.hajda@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=yang.lee@linux.alibaba.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