From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for GuC messaging enable/disable tweaks
Date: Wed, 19 Jun 2019 23:03:40 -0000 [thread overview]
Message-ID: <20190619230340.18134.27950@emeril.freedesktop.org> (raw)
In-Reply-To: <20190619214351.12000-1-daniele.ceraolospurio@intel.com>
== Series Details ==
Series: GuC messaging enable/disable tweaks
URL : https://patchwork.freedesktop.org/series/62412/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b1e56a188163 drm/i915/guc: reorder enable/disable communication steps
99d49d7e5f42 drm/i915/guc: handle GuC messages received with CTB disabled
-:97: CHECK:LINE_SPACING: Please don't use multiple blank lines
#97: FILE: drivers/gpu/drm/i915/intel_uc.c:268:
+
+
total: 0 errors, 0 warnings, 1 checks, 122 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:[~2019-06-19 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 21:43 [PATCH 0/2] GuC messaging enable/disable tweaks Daniele Ceraolo Spurio
2019-06-19 21:43 ` [PATCH 1/2] drm/i915/guc: reorder enable/disable communication steps Daniele Ceraolo Spurio
2019-06-19 23:22 ` Matthew Brost
2019-06-20 8:43 ` Michal Wajdeczko
2019-06-19 21:43 ` [PATCH 2/2] drm/i915/guc: handle GuC messages received with CTB disabled Daniele Ceraolo Spurio
2019-06-20 13:48 ` Chris Wilson
2019-06-20 17:55 ` Daniele Ceraolo Spurio
2019-06-19 23:03 ` Patchwork [this message]
2019-06-19 23:36 ` ✓ Fi.CI.BAT: success for GuC messaging enable/disable tweaks Patchwork
2019-06-20 14:45 ` ✓ 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=20190619230340.18134.27950@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniele.ceraolospurio@intel.com \
--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.