public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Prepare to split crtc state in uapi and hw state (rev2)
Date: Thu, 26 Sep 2019 10:08:13 -0000	[thread overview]
Message-ID: <20190926100813.6720.26678@emeril.freedesktop.org> (raw)
In-Reply-To: <20190925145901.3943-1-maarten.lankhorst@linux.intel.com>

== Series Details ==

Series: series starting with [1/4] drm/i915: Prepare to split crtc state in uapi and hw state (rev2)
URL   : https://patchwork.freedesktop.org/series/67227/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
1368d49f2ac9 drm/i915: Prepare to split crtc state in uapi and hw state
-:2130: CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#2130: FILE: drivers/gpu/drm/i915/display/intel_display.c:11264:
+	crtc_state->uapi.active = crtc_state->uapi.enable = true;

-:2837: CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#2837: FILE: drivers/gpu/drm/i915/display/intel_display.c:16735:
+		crtc_state->hw.active = crtc_state->hw.enable =

-:4001: ERROR:CODE_INDENT: code indent should use tabs where possible
#4001: FILE: drivers/gpu/drm/i915/display/intel_sprite.c:211:
+^I^I^I^I          new_crtc_state->uapi.event);$

-:4001: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#4001: FILE: drivers/gpu/drm/i915/display/intel_sprite.c:211:
+		drm_crtc_arm_vblank_event(&crtc->base,
+				          new_crtc_state->uapi.event);

total: 1 errors, 0 warnings, 3 checks, 4371 lines checked
e3721d7eec35 drm/i915: Handle a few more cases for hw/sw split
4e6a21fdedd8 drm/i915: Complete sw/hw split, v2.
-:15: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#15: 
- Clear crtc_state->hw on disable, instead of using clear_intel_crtc_state().

total: 0 errors, 1 warnings, 0 checks, 204 lines checked
a971c9fd2236 drm/i915: Remove begin/finish_crtc_commit, v3.
-:191: ERROR:CODE_INDENT: code indent should use tabs where possible
#191: FILE: drivers/gpu/drm/i915/display/intel_display.c:13821:
+        /*$

-:192: ERROR:CODE_INDENT: code indent should use tabs where possible
#192: FILE: drivers/gpu/drm/i915/display/intel_display.c:13822:
+         * We usually enable FIFO underrun interrupts as part of the$

-:193: ERROR:CODE_INDENT: code indent should use tabs where possible
#193: FILE: drivers/gpu/drm/i915/display/intel_display.c:13823:
+         * CRTC enable sequence during modesets.  But when we inherit a$

-:194: ERROR:CODE_INDENT: code indent should use tabs where possible
#194: FILE: drivers/gpu/drm/i915/display/intel_display.c:13824:
+         * valid pipe configuration from the BIOS we need to take care$

-:195: ERROR:CODE_INDENT: code indent should use tabs where possible
#195: FILE: drivers/gpu/drm/i915/display/intel_display.c:13825:
+         * of enabling them on the CRTC's first fastset.$

-:196: ERROR:CODE_INDENT: code indent should use tabs where possible
#196: FILE: drivers/gpu/drm/i915/display/intel_display.c:13826:
+         */$

total: 6 errors, 0 warnings, 0 checks, 247 lines checked

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-09-26 10:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 14:58 [PATCH 1/4] drm/i915: Prepare to split crtc state in uapi and hw state Maarten Lankhorst
2019-09-25 14:58 ` [PATCH 2/4] drm/i915: Handle a few more cases for hw/sw split Maarten Lankhorst
2019-09-25 14:59 ` [PATCH 3/4] drm/i915: Complete sw/hw split, v2 Maarten Lankhorst
2019-09-25 21:41   ` Matt Roper
2019-09-25 14:59 ` [PATCH 4/4] drm/i915: Remove begin/finish_crtc_commit, v2 Maarten Lankhorst
2019-09-25 15:23   ` Ville Syrjälä
2019-09-25 21:42   ` Matt Roper
2019-09-26  8:46     ` Maarten Lankhorst
2019-09-26  9:22     ` Maarten Lankhorst
2019-09-26  9:47     ` [PATCH] drm/i915: Remove begin/finish_crtc_commit, v3 Maarten Lankhorst
2019-09-26 16:22       ` Ville Syrjälä
2019-09-27  8:29         ` Maarten Lankhorst
2019-09-26 12:45     ` [PATCH 4/4] drm/i915: Remove begin/finish_crtc_commit, v2 Ville Syrjälä
2019-09-25 16:47 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Prepare to split crtc state in uapi and hw state Patchwork
2019-09-25 17:15 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-26  9:29 ` ✓ Fi.CI.IGT: " Patchwork
2019-09-26 10:08 ` Patchwork [this message]
2019-09-26 10:42 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915: Prepare to split crtc state in uapi and hw state (rev2) Patchwork
2019-09-27  6:18 ` ✓ 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=20190926100813.6720.26678@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@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