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/gtt: Replace struct_mutex serialisation for allocation
Date: Mon, 03 Jun 2019 17:18:09 -0000 [thread overview]
Message-ID: <20190603171809.25578.93336@emeril.freedesktop.org> (raw)
In-Reply-To: <20190603171130.3186-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/gtt: Replace struct_mutex serialisation for allocation
URL : https://patchwork.freedesktop.org/series/61533/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d6226b7f1918 drm/i915/gtt: Replace struct_mutex serialisation for allocation
-:495: CHECK:UNCOMMENTED_DEFINITION: spinlock_t definition without comment
#495: FILE: drivers/gpu/drm/i915/i915_gem_gtt.h:259:
+ spinlock_t lock;
-:503: CHECK:UNCOMMENTED_DEFINITION: spinlock_t definition without comment
#503: FILE: drivers/gpu/drm/i915/i915_gem_gtt.h:266:
+ spinlock_t lock;
-:509: CHECK:UNCOMMENTED_DEFINITION: spinlock_t definition without comment
#509: FILE: drivers/gpu/drm/i915/i915_gem_gtt.h:272:
+ spinlock_t lock;
total: 0 errors, 0 warnings, 3 checks, 463 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-06-03 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 17:11 [PATCH] drm/i915/gtt: Replace struct_mutex serialisation for allocation Chris Wilson
2019-06-03 17:18 ` Patchwork [this message]
2019-06-03 17:19 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-06-03 17:39 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-04 8:21 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-04 11:37 ` [PATCH] " Joonas Lahtinen
2019-06-04 11:42 ` 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=20190603171809.25578.93336@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