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/guc: Clear preempt status before use (rev2)
Date: Fri, 12 Oct 2018 16:40:15 -0000 [thread overview]
Message-ID: <20181012164015.1371.45986@emeril.freedesktop.org> (raw)
In-Reply-To: <20181012152511.30809-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/guc: Clear preempt status before use (rev2)
URL : https://patchwork.freedesktop.org/series/50936/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9aca37eb0037 drm/i915/guc: Clear preempt status before use
-:8: WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
-:58: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 1 warnings, 0 checks, 44 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-10-12 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 15:25 [PATCH] drm/i915/guc: Clear preempt status before use Chris Wilson
2018-10-12 15:58 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-10-12 16:20 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-12 16:33 ` [PATCH] " Chris Wilson
2018-10-12 16:40 ` Patchwork [this message]
2018-10-12 16:58 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Clear preempt status before use (rev2) Patchwork
2018-10-12 17:06 ` [PATCH] drm/i915/guc: Clear preempt status before use Chris Wilson
2018-10-12 17:17 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Clear preempt status before use (rev3) Patchwork
2018-10-12 17:33 ` ✗ Fi.CI.BAT: failure " 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=20181012164015.1371.45986@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 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.