From: Patchwork <patchwork@emeril.freedesktop.org>
To: kiran.s.kumar@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915: FBC needs vblank before enable / disable. (rev2)
Date: Wed, 03 Apr 2019 04:52:00 -0000 [thread overview]
Message-ID: <20190403045200.4271.55581@emeril.freedesktop.org> (raw)
In-Reply-To: <1554265825-31346-1-git-send-email-kiran.s.kumar@intel.com>
== Series Details ==
Series: drm/i915: FBC needs vblank before enable / disable. (rev2)
URL : https://patchwork.freedesktop.org/series/58843/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a7eb63398cfa drm/i915: FBC needs vblank before enable / disable.
-:10: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#10:
several control signals in the compression engine also will fail to properly
-:26: ERROR:GERRIT_CHANGE_ID: Remove Gerrit Change-Id's before submitting upstream.
#26:
Change-Id: I2465610bb0a82df99e5c53b1eb4ed74565996b1e
total: 1 errors, 1 warnings, 0 checks, 20 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:[~2019-04-03 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 4:30 [PATCH] drm/i915: FBC needs vblank before enable / disable kiran.s.kumar
2019-04-03 4:52 ` Patchwork [this message]
2019-04-03 5:10 ` ✗ Fi.CI.BAT: failure for drm/i915: FBC needs vblank before enable / disable. (rev2) Patchwork
2019-04-03 17:54 ` [PATCH] drm/i915: FBC needs vblank before enable / disable Souza, Jose
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=20190403045200.4271.55581@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kiran.s.kumar@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