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 drm/i915: Check for I915_MODE_FLAG_INHERITED before drm_atomic_helper_check_modeset
Date: Wed, 21 Feb 2018 09:40:57 -0000 [thread overview]
Message-ID: <20180221094057.14809.85432@emeril.freedesktop.org> (raw)
In-Reply-To: <20180221092808.30060-1-maarten.lankhorst@linux.intel.com>
== Series Details ==
Series: drm/i915: Check for I915_MODE_FLAG_INHERITED before drm_atomic_helper_check_modeset
URL : https://patchwork.freedesktop.org/series/38678/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a339d719bb21 drm/i915: Check for I915_MODE_FLAG_INHERITED before drm_atomic_helper_check_modeset
-:25: WARNING: line over 80 characters
#25: FILE: drivers/gpu/drm/i915/intel_display.c:12036:
+ for_each_oldnew_crtc_in_state(state, crtc, old_crtc_state, crtc_state, i)
-:26: WARNING: line over 80 characters
#26: FILE: drivers/gpu/drm/i915/intel_display.c:12037:
+ if (crtc_state->mode.private_flags != old_crtc_state->mode.private_flags)
total: 0 errors, 2 warnings, 0 checks, 44 lines checked
_______________________________________________
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-21 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 9:28 [PATCH] drm/i915: Check for I915_MODE_FLAG_INHERITED before drm_atomic_helper_check_modeset Maarten Lankhorst
2018-02-21 9:40 ` Patchwork [this message]
2018-02-21 9:55 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-02-21 12:40 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2018-02-21 12:54 ` ✗ Fi.CI.BAT: " Patchwork
2018-02-21 23:12 ` [PATCH] " Lyude Paul
2018-03-02 2:03 ` Lyude Paul
2018-03-02 9:37 ` Jani Nikula
2018-03-02 10:14 ` Lofstedt, Marta
2018-03-02 19:59 ` ✗ Fi.CI.BAT: failure for " 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=20180221094057.14809.85432@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 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.