From: Patchwork <patchwork@emeril.freedesktop.org>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Shortcut readiness to reset check
Date: Fri, 12 Apr 2019 15:54:21 -0000 [thread overview]
Message-ID: <20190412155421.11258.61808@emeril.freedesktop.org> (raw)
In-Reply-To: <20190412153723.31931-1-mika.kuoppala@linux.intel.com>
== Series Details ==
Series: series starting with [1/3] drm/i915: Shortcut readiness to reset check
URL : https://patchwork.freedesktop.org/series/59406/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b2a7ac10e21f drm/i915: Shortcut readiness to reset check
-:9: ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Chris Wilson <chris@chris-wilson.co.uk'
#9:
Cc: Chris Wilson <chris@chris-wilson.co.uk
total: 1 errors, 0 warnings, 0 checks, 13 lines checked
66e5bb3569cc drm/i915: Handle catastrophic error on engine reset
7a1a2e7ea0f4 drm/i915: Log catastrophic errors on gen11
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-12 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 15:37 [PATCH 1/3] drm/i915: Shortcut readiness to reset check Mika Kuoppala
2019-04-12 15:37 ` [PATCH 2/3] drm/i915: Handle catastrophic error on engine reset Mika Kuoppala
2019-04-12 15:49 ` Chris Wilson
2019-04-12 15:58 ` Mika Kuoppala
2019-04-12 15:37 ` [PATCH 3/3] drm/i915: Log catastrophic errors on gen11 Mika Kuoppala
2019-04-12 15:42 ` Chris Wilson
2019-04-12 15:47 ` Mika Kuoppala
2019-04-12 15:53 ` Chris Wilson
2019-04-12 15:51 ` [PATCH 1/3] drm/i915: Shortcut readiness to reset check Chris Wilson
2019-04-12 15:54 ` Patchwork [this message]
2019-04-12 16:32 ` ✓ Fi.CI.BAT: success for series starting with [1/3] " Patchwork
2019-04-12 19:38 ` ✓ 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=20190412155421.11258.61808@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox