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/execlists: Force write serialisation into context image vs execution
Date: Thu, 08 Nov 2018 08:33:28 -0000 [thread overview]
Message-ID: <20181108083328.20370.87586@emeril.freedesktop.org> (raw)
In-Reply-To: <20181108081740.25615-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/3] drm/i915/execlists: Force write serialisation into context image vs execution
URL : https://patchwork.freedesktop.org/series/52209/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
719262fc8e08 drm/i915/execlists: Force write serialisation into context image vs execution
60eed560af03 drm/i915: Return immediately if trylock fails for direct-reclaim
227c8bdf97a3 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")
-:240: ERROR:LOCKING: recursive locking is bad, do not use this ever.
#240: FILE: drivers/gpu/drm/i915/i915_gem_userptr.c:108:
+ switch (mutex_trylock_recursive(m)) {
total: 2 errors, 1 warnings, 0 checks, 444 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-11-08 8:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 8:17 [PATCH 1/3] drm/i915/execlists: Force write serialisation into context image vs execution Chris Wilson
2018-11-08 8:17 ` [PATCH 2/3] drm/i915: Return immediately if trylock fails for direct-reclaim Chris Wilson
2018-11-08 16:23 ` Tvrtko Ursulin
2018-11-08 16:48 ` Chris Wilson
2018-11-09 7:30 ` Tvrtko Ursulin
2018-11-09 11:44 ` Chris Wilson
2018-11-13 10:24 ` Tvrtko Ursulin
2018-11-13 17:10 ` Chris Wilson
2018-11-15 11:39 ` Tvrtko Ursulin
2018-11-08 8:17 ` [PATCH 3/3] drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start Chris Wilson
2018-11-08 16:45 ` Tvrtko Ursulin
2018-11-08 8:33 ` Patchwork [this message]
2018-11-08 9:07 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915/execlists: Force write serialisation into context image vs execution Patchwork
2018-11-08 12:00 ` [PATCH 1/3] " Mika Kuoppala
2018-11-08 12:11 ` Chris Wilson
2018-11-08 12:13 ` Mika Kuoppala
2018-11-08 12:26 ` Chris Wilson
2018-11-08 13:38 ` Chris Wilson
2018-11-08 19:51 ` ✓ Fi.CI.IGT: success for series starting with [1/3] " 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=20181108083328.20370.87586@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox