From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Default request/fence expiry + watchdog (rev5)
Date: Wed, 24 Mar 2021 13:16:48 -0000 [thread overview]
Message-ID: <161659180852.19036.1948952778297658102@emeril.freedesktop.org> (raw)
In-Reply-To: <20210324121335.2307063-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: Default request/fence expiry + watchdog (rev5)
URL : https://patchwork.freedesktop.org/series/87930/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8fc435bf4d9f drm/i915: Extract active lookup engine to a helper
-:114: CHECK:LINE_SPACING: Please don't use multiple blank lines
#114: FILE: drivers/gpu/drm/i915/i915_request.c:290:
+
+
total: 0 errors, 0 warnings, 1 checks, 104 lines checked
eee19b9617fc drm/i915: Individual request cancellation
263ce11450a2 drm/i915: Restrict sentinel requests further
9d6ef50b29a0 drm/i915: Handle async cancellation in sentinel assert
d0d85357b1fb drm/i915: Request watchdog infrastructure
22d460cbf87f drm/i915: Fail too long user submissions by default
d81b27e279a2 drm/i915: Allow configuring default request expiry via modparam
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-24 13:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 12:13 [PATCH v4 0/7] Default request/fence expiry + watchdog Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 12:13 ` [PATCH 1/7] drm/i915: Extract active lookup engine to a helper Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 12:21 ` Matthew Auld
2021-03-24 12:21 ` Matthew Auld
2021-03-24 12:13 ` [PATCH 2/7] drm/i915: Individual request cancellation Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 15:24 ` Matthew Auld
2021-03-24 15:24 ` Matthew Auld
2021-03-24 12:13 ` [PATCH 3/7] drm/i915: Restrict sentinel requests further Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 15:25 ` Matthew Auld
2021-03-24 15:25 ` [Intel-gfx] " Matthew Auld
2021-03-26 0:01 ` Daniel Vetter
2021-03-26 0:01 ` Daniel Vetter
2021-03-24 12:13 ` [PATCH 4/7] drm/i915: Handle async cancellation in sentinel assert Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 17:22 ` Matthew Auld
2021-03-24 17:22 ` Matthew Auld
2021-03-24 12:13 ` [PATCH 5/7] drm/i915: Request watchdog infrastructure Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-26 0:00 ` Daniel Vetter
2021-03-26 0:00 ` [Intel-gfx] " Daniel Vetter
2021-03-26 10:32 ` Tvrtko Ursulin
2021-03-26 10:32 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 12:13 ` [PATCH 6/7] drm/i915: Fail too long user submissions by default Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-24 12:13 ` [PATCH 7/7] drm/i915: Allow configuring default request expiry via modparam Tvrtko Ursulin
2021-03-24 12:13 ` [Intel-gfx] " Tvrtko Ursulin
2021-03-26 0:25 ` Daniel Vetter
2021-03-26 0:25 ` [Intel-gfx] " Daniel Vetter
2021-03-24 13:16 ` Patchwork [this message]
2021-03-24 13:21 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for Default request/fence expiry + watchdog (rev5) Patchwork
2021-03-24 13:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-24 23:29 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-03-26 9:10 ` [Intel-gfx] [PATCH v4 0/7] Default request/fence expiry + watchdog Daniel Vetter
2021-03-26 9:10 ` Daniel Vetter
2021-03-26 10:31 ` Tvrtko Ursulin
2021-03-26 10:31 ` Tvrtko Ursulin
2021-04-08 10:18 ` Daniel Vetter
2021-04-08 10:18 ` Daniel Vetter
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=161659180852.19036.1948952778297658102@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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.