Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 series starting with [1/2] drm/i915/guc: Implement reset locally
Date: Mon, 08 Apr 2019 22:51:02 -0000	[thread overview]
Message-ID: <20190408225102.21095.97763@emeril.freedesktop.org> (raw)
In-Reply-To: <20190408223857.7035-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/2] drm/i915/guc: Implement reset locally
URL   : https://patchwork.freedesktop.org/series/59199/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
ed8431824b19 drm/i915/guc: Implement reset locally
8b244698e9bc drm/i915/execlists: Always reset the context's RING registers
-:17: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#17: 
    <0> [412.390350]   <idle>-0       3d.s2 408373352us : __i915_request_submit: rcs0 fence 1e95b:3640 -> current 3638

total: 0 errors, 1 warnings, 0 checks, 296 lines checked

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-04-08 22:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 22:38 [PATCH 1/2] drm/i915/guc: Implement reset locally Chris Wilson
2019-04-08 22:38 ` [PATCH 2/2] drm/i915/execlists: Always reset the context's RING registers Chris Wilson
2019-04-10 14:40   ` Mika Kuoppala
2019-04-10 14:46     ` Chris Wilson
2019-04-08 22:51 ` Patchwork [this message]
2019-04-08 23:52 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/guc: Implement reset locally Patchwork
2019-04-09  6:25 ` ✓ Fi.CI.IGT: " Patchwork
2019-04-11 12:57 ` [PATCH 1/2] " Mika Kuoppala

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=20190408225102.21095.97763@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