From: Patchwork <patchwork@emeril.freedesktop.org>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/icl: Fix MG_DP_MODE() register programming
Date: Fri, 19 Apr 2019 07:27:48 -0000 [thread overview]
Message-ID: <20190419072748.29310.50681@emeril.freedesktop.org> (raw)
In-Reply-To: <20190419071026.32370-1-imre.deak@intel.com>
== Series Details ==
Series: drm/i915/icl: Fix MG_DP_MODE() register programming
URL : https://patchwork.freedesktop.org/series/59744/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d26cc79d0b12 drm/i915/icl: Fix MG_DP_MODE() register programming
-:12: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#12:
37fc7845df7b6 ("drm/i915: Call MG_DP_MODE() macro with the right parameters order")
-:12: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 37fc7845df7b ("drm/i915: Call MG_DP_MODE() macro with the right parameters order")'
#12:
37fc7845df7b6 ("drm/i915: Call MG_DP_MODE() macro with the right parameters order")
total: 1 errors, 1 warnings, 0 checks, 50 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-19 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 7:10 [PATCH] drm/i915/icl: Fix MG_DP_MODE() register programming Imre Deak
2019-04-19 7:27 ` Patchwork [this message]
2019-04-19 7:46 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-04-19 8:55 ` ✓ Fi.CI.IGT: " Patchwork
2019-04-23 8:13 ` Imre Deak
2019-04-19 16:02 ` [PATCH] " Souza, Jose
2019-04-19 16:04 ` Imre Deak
2019-04-19 16:29 ` Souza, Jose
2019-04-19 17:01 ` Imre Deak
2019-04-22 16:15 ` Lucas De Marchi
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=20190419072748.29310.50681@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=imre.deak@intel.com \
--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