From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/4] drm/i915: Also check view->type for a normal GGTT view
Date: Tue, 20 Feb 2018 14:49:24 -0000 [thread overview]
Message-ID: <20180220144924.25065.8167@emeril.freedesktop.org> (raw)
In-Reply-To: <20180220134208.24988-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [v2,1/4] drm/i915: Also check view->type for a normal GGTT view
URL : https://patchwork.freedesktop.org/series/38593/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
4a4061e50613 drm/i915: Also check view->type for a normal GGTT view
17780b820d0b drm/i915: Move the policy for placement of the GGTT vma into the caller
-:28: WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#28:
<4>[ 227.152102] Modules linked in: i915 snd_hda_codec_analog snd_hda_codec_generic coretemp snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm lpc_ich e1000e mei_me mei prime_numbers
-:230: WARNING: line over 80 characters
#230: FILE: drivers/gpu/drm/i915/intel_display.c:12738:
+ &to_intel_plane_state(new_state)->flags);
-:250: WARNING: line over 80 characters
#250: FILE: drivers/gpu/drm/i915/intel_display.c:13156:
+ &to_intel_plane_state(new_plane_state)->flags);
-:260: WARNING: line over 80 characters
#260: FILE: drivers/gpu/drm/i915/intel_display.c:13188:
+ to_intel_plane_state(old_plane_state)->flags);
total: 0 errors, 4 warnings, 0 checks, 240 lines checked
a08e423e1cbd drm/i915/fbdev: Use the PLANE_HAS_FENCE flags from the time of pinning
1a6dad4878b4 drm/i915/fbc: Use PLANE_HAS_FENCE to determine if the plane is fenced
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-20 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 13:42 [PATCH v2 1/4] drm/i915: Also check view->type for a normal GGTT view Chris Wilson
2018-02-20 13:42 ` [PATCH v2 2/4] drm/i915: Move the policy for placement of the GGTT vma into the caller Chris Wilson
2018-02-20 13:42 ` [PATCH v2 3/4] drm/i915/fbdev: Use the PLANE_HAS_FENCE flags from the time of pinning Chris Wilson
2018-02-20 13:56 ` Ville Syrjälä
2018-02-20 13:42 ` [PATCH v2 4/4] drm/i915/fbc: Use PLANE_HAS_FENCE to determine if the plane is fenced Chris Wilson
2018-02-20 13:59 ` Ville Syrjälä
2018-02-20 14:02 ` Chris Wilson
2018-02-20 14:49 ` Patchwork [this message]
2018-02-20 15:04 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm/i915: Also check view->type for a normal GGTT view Patchwork
2018-02-20 20:36 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-02-20 20:39 ` Chris Wilson
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=20180220144924.25065.8167@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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