From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Use trylock instead of blocking lock for __i915_gem_free_objects.
Date: Wed, 22 Dec 2021 16:28:22 -0000 [thread overview]
Message-ID: <164019050272.15677.15636067382775756342@emeril.freedesktop.org> (raw)
In-Reply-To: <20211222155622.2960379-1-maarten.lankhorst@linux.intel.com>
== Series Details ==
Series: drm/i915: Use trylock instead of blocking lock for __i915_gem_free_objects.
URL : https://patchwork.freedesktop.org/series/98306/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
dfcddd530d5e drm/i915: Use trylock instead of blocking lock for __i915_gem_free_objects.
-:37: WARNING:LONG_LINE: line length of 104 exceeds 100 columns
#37: FILE: drivers/gpu/drm/i915/gem/i915_gem_object.c:337:
+ queue_delayed_work(i915->wq, &i915->mm.free_work, msecs_to_jiffies(10));
total: 0 errors, 1 warnings, 0 checks, 54 lines checked
next prev parent reply other threads:[~2021-12-22 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 15:56 [PATCH] drm/i915: Use trylock instead of blocking lock for __i915_gem_free_objects Maarten Lankhorst
2021-12-22 15:56 ` [Intel-gfx] " Maarten Lankhorst
2021-12-22 16:28 ` Patchwork [this message]
2021-12-22 16:29 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2021-12-22 16:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-22 19:31 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-12-22 19:43 ` [Intel-gfx] [PATCH] " Thomas Hellström (Intel)
2021-12-23 11:31 ` Maarten Lankhorst
2021-12-22 20:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Use trylock instead of blocking lock for __i915_gem_free_objects. (rev2) Patchwork
2021-12-22 20:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-22 21:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-22 22:42 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=164019050272.15677.15636067382775756342@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
/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.