From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] drm/i915: Restore vblank interrupts earlier (rev4)
Date: Wed, 03 Oct 2018 15:54:04 -0000 [thread overview]
Message-ID: <20181003155404.18505.84250@emeril.freedesktop.org> (raw)
In-Reply-To: <20181001142909.5567-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: series starting with [v2,1/3] drm/i915: Restore vblank interrupts earlier (rev4)
URL : https://patchwork.freedesktop.org/series/50393/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c6a938a3e0a7 drm/i915: Restore vblank interrupts earlier
d5a5d74e82b0 drm/i915: Use the correct crtc when sanitizing plane mapping
-:34: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#34:
Cc: stable@vger.kernel.org # fcba862e8428 drm/i915: Have plane->get_hw_state() return the current pipe
total: 0 errors, 1 warnings, 0 checks, 155 lines checked
b1aa286906d2 drm/i915: Clean up early plane debugs
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-03 15:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 14:29 [PATCH 1/3] drm/i915: Restore vblank interrupts earlier Ville Syrjala
2018-10-01 14:31 ` [PATCH 2/3] drm/i915: Use the correct crtc when sanitizing plane mapping Ville Syrjala
2018-10-02 12:11 ` [Intel-gfx] " Daniel Vetter
2018-10-02 12:11 ` Daniel Vetter
2018-10-02 14:21 ` Ville Syrjälä
2018-10-02 14:21 ` Ville Syrjälä
2018-10-03 8:53 ` [Intel-gfx] " Daniel Vetter
2018-10-03 8:53 ` Daniel Vetter
2018-10-03 14:32 ` Ville Syrjälä
2018-10-03 14:32 ` Ville Syrjälä
2018-10-03 14:50 ` [PATCH v2 " Ville Syrjala
2018-10-03 14:50 ` Ville Syrjala
2018-10-03 16:12 ` Daniel Vetter
2018-10-03 16:12 ` Daniel Vetter
2018-10-04 17:24 ` Ville Syrjälä
2018-10-04 17:24 ` Ville Syrjälä
2018-10-01 14:31 ` [PATCH 3/3] drm/i915: Clean up early plane debugs Ville Syrjala
2018-10-02 12:21 ` Daniel Vetter
2018-10-02 14:42 ` [Intel-gfx] " Ville Syrjälä
2018-10-03 14:50 ` [PATCH v2 " Ville Syrjala
2018-10-03 16:12 ` [Intel-gfx] " Daniel Vetter
2018-10-01 15:19 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Restore vblank interrupts earlier Patchwork
2018-10-01 15:43 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-01 16:56 ` ✓ Fi.CI.IGT: " Patchwork
2018-10-02 8:48 ` [PATCH 1/3] " Daniel Vetter
2018-10-02 8:48 ` Daniel Vetter
2018-10-03 14:49 ` [PATCH v2 " Ville Syrjala
2018-10-03 15:54 ` Patchwork [this message]
2018-10-03 16:25 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/3] drm/i915: Restore vblank interrupts earlier (rev4) Patchwork
2018-10-04 7:34 ` ✓ 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=20181003155404.18505.84250@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.