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 drm/i915: Do not use iowait while waiting for the GPU
Date: Fri, 27 Jul 2018 19:35:34 -0000 [thread overview]
Message-ID: <20180727193534.31055.2422@emeril.freedesktop.org> (raw)
In-Reply-To: <20180727184312.29937-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Do not use iowait while waiting for the GPU
URL : https://patchwork.freedesktop.org/series/47363/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9323b39a7901 drm/i915: Do not use iowait while waiting for the GPU
-:14: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#14:
References: 52ccc4314293 ("cpufreq: intel_pstate: HWP boost performance on IO wakeup")
-:14: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 52ccc4314293 ("cpufreq: intel_pstate: HWP boost performance on IO wakeup")'
#14:
References: 52ccc4314293 ("cpufreq: intel_pstate: HWP boost performance on IO wakeup")
total: 1 errors, 1 warnings, 0 checks, 8 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-07-27 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 18:43 [PATCH] drm/i915: Do not use iowait while waiting for the GPU Chris Wilson
2018-07-27 18:58 ` Chris Wilson
2018-07-27 19:35 ` Patchwork [this message]
2018-07-27 19:55 ` Chris Wilson
2018-07-27 19:56 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-07-27 20:51 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Do not use iowait while waiting for the GPU (rev2) Patchwork
2018-07-27 21:14 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-28 5:20 ` [PATCH] drm/i915: Do not use iowait while waiting for the GPU Francisco Jerez
2018-07-28 14:22 ` Chris Wilson
2018-07-28 20:18 ` Francisco Jerez
2018-07-28 20:58 ` Chris Wilson
2018-07-29 19:29 ` Francisco Jerez
2018-07-30 12:56 ` Chris Wilson
2018-07-30 18:55 ` Francisco Jerez
2018-07-28 16:27 ` 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=20180727193534.31055.2422@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.