intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: remove excess line continuation backslashes
Date: Wed, 14 Nov 2018 13:48:37 +0200	[thread overview]
Message-ID: <87wopfj2wa.fsf@intel.com> (raw)
In-Reply-To: <20181114113502.GM9144@intel.com>

On Wed, 14 Nov 2018, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Nov 14, 2018 at 01:21:30PM +0200, Jani Nikula wrote:
>> While removing .palette_offsets, I removed the commas after
>> .trans_offsets in the macros, but failed to remove the line continuation
>> backslashes.
>> 
>> While at it, also remove another extra comma to be in line with the
>> other related macros.
>
> In general I like having the comma after the last element in an
> array/enum/whatever. In this case it doesn't really matter, but
> in cases like
>
>   enum {
>   	yes,
>   	no,
> + 	maybe,
>   };
>
> it will result in a cleaner diff.

Totally agreed; it just doesn't make a difference here, and none of the
other places here have it, so off it goes.

> Anyways, patch is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks. /me looks at CI expectantly.

BR,
Jani.

>
>> 
>> Fixes: 74c1e826427a ("drm/i915: remove palette_offsets from device info in favor of _PICK()")
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/i915/i915_pci.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
>> index 4ccab8372dd4..983ae7fd8217 100644
>> --- a/drivers/gpu/drm/i915/i915_pci.c
>> +++ b/drivers/gpu/drm/i915/i915_pci.c
>> @@ -36,13 +36,13 @@
>>  	.pipe_offsets = { PIPE_A_OFFSET, PIPE_B_OFFSET, \
>>  			  PIPE_C_OFFSET, PIPE_EDP_OFFSET }, \
>>  	.trans_offsets = { TRANSCODER_A_OFFSET, TRANSCODER_B_OFFSET, \
>> -			   TRANSCODER_C_OFFSET, TRANSCODER_EDP_OFFSET } \
>> +			   TRANSCODER_C_OFFSET, TRANSCODER_EDP_OFFSET }
>>  
>>  #define GEN_CHV_PIPEOFFSETS \
>>  	.pipe_offsets = { PIPE_A_OFFSET, PIPE_B_OFFSET, \
>>  			  CHV_PIPE_C_OFFSET }, \
>>  	.trans_offsets = { TRANSCODER_A_OFFSET, TRANSCODER_B_OFFSET, \
>> -			   CHV_TRANSCODER_C_OFFSET, } \
>> +			   CHV_TRANSCODER_C_OFFSET }
>>  
>>  #define CURSOR_OFFSETS \
>>  	.cursor_offsets = { CURSOR_A_OFFSET, CURSOR_B_OFFSET, CHV_CURSOR_C_OFFSET }
>> -- 
>> 2.11.0

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-11-14 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 11:21 [PATCH] drm/i915: remove excess line continuation backslashes Jani Nikula
2018-11-14 11:35 ` Ville Syrjälä
2018-11-14 11:48   ` Jani Nikula [this message]
2018-11-15 11:54     ` Jani Nikula
2018-11-14 14:13 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-11-14 15:01 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-15 11:21 ` ✓ Fi.CI.IGT: " Patchwork

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=87wopfj2wa.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).