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/3] drm/i915: Prevent concurrent GGTT update and use on Braswell (again)
Date: Mon, 14 Jan 2019 21:32:02 -0000 [thread overview]
Message-ID: <20190114213202.24565.99158@emeril.freedesktop.org> (raw)
In-Reply-To: <20190114211729.30352-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/3] drm/i915: Prevent concurrent GGTT update and use on Braswell (again)
URL : https://patchwork.freedesktop.org/series/55201/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
071bbd0707df drm/i915: Prevent concurrent GGTT update and use on Braswell (again)
-:14: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 5bab6f60cb4d ("drm/i915: Serialise updates to GGTT with access through GGTT on Braswell")'
#14:
commit 5bab6f60cb4d1417ad7c599166bcfec87529c1a2
-:22: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 4509276ee824 ("drm/i915: Remove Braswell GGTT update w/a")'
#22:
commit 4509276ee824bb967885c095c610767e42345c36
-:39: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#39:
References: 5bab6f60cb4d ("drm/i915: Serialise updates to GGTT with access through GGTT on Braswell")
-:39: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 5bab6f60cb4d ("drm/i915: Serialise updates to GGTT with access through GGTT on Braswell")'
#39:
References: 5bab6f60cb4d ("drm/i915: Serialise updates to GGTT with access through GGTT on Braswell")
-:40: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 4509276ee824 ("drm/i915: Remove Braswell GGTT update w/a")'
#40:
References: 4509276ee824 ("drm/i915: Remove Braswell GGTT update w/a")
total: 4 errors, 1 warnings, 0 checks, 9 lines checked
b69127d2d857 drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start
-:23: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#23:
References: 93065ac753e4 ("mm, oom: distinguish blockable mode for mmu notifiers")
-:23: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 93065ac753e4 ("mm, oom: distinguish blockable mode for mmu notifiers")'
#23:
References: 93065ac753e4 ("mm, oom: distinguish blockable mode for mmu notifiers")
-:241: ERROR:LOCKING: recursive locking is bad, do not use this ever.
#241: FILE: drivers/gpu/drm/i915/i915_gem_userptr.c:105:
+ switch (mutex_trylock_recursive(m)) {
total: 2 errors, 1 warnings, 0 checks, 442 lines checked
14241cdbf4bd drm/i915/userptr: Probe vma range before gup
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-14 21:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 21:17 [PATCH 1/3] drm/i915: Prevent concurrent GGTT update and use on Braswell (again) Chris Wilson
2019-01-14 21:17 ` [PATCH 2/3] drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start Chris Wilson
2019-01-15 9:47 ` Tvrtko Ursulin
2019-01-15 10:00 ` Chris Wilson
2019-01-15 11:25 ` Tvrtko Ursulin
2019-01-15 11:54 ` Tvrtko Ursulin
2019-01-15 11:58 ` Chris Wilson
2019-01-14 21:17 ` [PATCH 3/3] drm/i915/userptr: Probe vma range before gup Chris Wilson
2019-01-15 10:19 ` Tvrtko Ursulin
2019-01-15 10:30 ` Chris Wilson
2019-01-15 10:40 ` Tvrtko Ursulin
2019-01-15 11:59 ` Chris Wilson
2019-01-15 10:27 ` Tvrtko Ursulin
2019-01-15 10:41 ` Chris Wilson
2019-01-15 10:52 ` Tvrtko Ursulin
2019-01-15 12:03 ` Chris Wilson
2019-01-14 21:32 ` Patchwork [this message]
2019-01-14 21:58 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Prevent concurrent GGTT update and use on Braswell (again) Patchwork
2019-01-15 3:58 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-15 9:04 ` [PATCH 1/3] " Tvrtko Ursulin
2019-01-15 9:28 ` 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=20190114213202.24565.99158@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.