All of lore.kernel.org
 help / color / mirror / Atom feed
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 [1/4] drm/i915: Also check view->type for a normal GGTT view
Date: Tue, 20 Feb 2018 13:03:49 -0000	[thread overview]
Message-ID: <20180220130349.25064.71173@emeril.freedesktop.org> (raw)
In-Reply-To: <20180220122452.5404-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/4] drm/i915: Also check view->type for a normal GGTT view
URL   : https://patchwork.freedesktop.org/series/38585/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
284097cf5955 drm/i915: Also check view->type for a normal GGTT view
8844508256ff 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

-:227: WARNING: line over 80 characters
#227: FILE: drivers/gpu/drm/i915/intel_display.c:12738:
+						 &to_intel_plane_state(new_state)->flags);

-:247: WARNING: line over 80 characters
#247: FILE: drivers/gpu/drm/i915/intel_display.c:13156:
+						 &to_intel_plane_state(new_plane_state)->flags);

-:257: WARNING: line over 80 characters
#257: 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
18f6e6de125e drm/i915/fbdev: Use the PLANE_HAS_FENCE flags from the time of pinning
d244e81a7063 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

  parent reply	other threads:[~2018-02-20 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 12:24 [PATCH 1/4] drm/i915: Also check view->type for a normal GGTT view Chris Wilson
2018-02-20 12:24 ` [PATCH 2/4] drm/i915: Move the policy for placement of the GGTT vma into the caller Chris Wilson
2018-02-20 12:24 ` [PATCH 3/4] drm/i915/fbdev: Use the PLANE_HAS_FENCE flags from the time of pinning Chris Wilson
2018-02-20 12:24 ` [PATCH 4/4] drm/i915/fbc: Use PLANE_HAS_FENCE to determine if the plane is fenced Chris Wilson
2018-02-20 13:03 ` Patchwork [this message]
2018-02-20 13:20 ` ✗ Fi.CI.BAT: warning for series starting with [1/4] drm/i915: Also check view->type for a normal GGTT view 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=20180220130349.25064.71173@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 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.