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: Signal the fences as they are cancelled due to wedging
Date: Thu, 29 Nov 2018 10:16:24 -0000 [thread overview]
Message-ID: <20181129101624.5825.66527@emeril.freedesktop.org> (raw)
In-Reply-To: <20181129093342.31537-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Signal the fences as they are cancelled due to wedging
URL : https://patchwork.freedesktop.org/series/53226/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b2cb1720bfa2 drm/i915: Signal the fences as they are cancelled due to wedging
-:13: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#13:
<1>[ 354.473346] BUG: unable to handle kernel NULL pointer dereference at 0000000000000250
total: 0 errors, 1 warnings, 0 checks, 67 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-29 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 9:33 [PATCH] drm/i915: Signal the fences as they are cancelled due to wedging Chris Wilson
2018-11-29 10:16 ` Patchwork [this message]
2018-11-29 10:32 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-11-29 12:50 ` [PATCH v2] " Chris Wilson
2018-11-29 13:11 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Signal the fences as they are cancelled due to wedging (rev2) Patchwork
2018-11-29 13:33 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-29 18:19 ` ✗ Fi.CI.IGT: failure for drm/i915: Signal the fences as they are cancelled due to wedging Patchwork
2018-11-29 23:44 ` ✗ Fi.CI.IGT: failure for drm/i915: Signal the fences as they are cancelled due to wedging (rev2) 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=20181129101624.5825.66527@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