Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/tracing: Enable user interrupts while intel_engine_notify is active (rev2)
Date: Thu, 09 Aug 2018 09:29:30 -0000	[thread overview]
Message-ID: <20180809092930.3702.3430@emeril.freedesktop.org> (raw)
In-Reply-To: <20180808151424.5183-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: drm/i915/tracing: Enable user interrupts while intel_engine_notify is active (rev2)
URL   : https://patchwork.freedesktop.org/series/47897/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
dea5a6eb6bc8 drm/i915/tracing: Enable user interrupts while intel_engine_notify is active
-:155: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#155: FILE: drivers/gpu/drm/i915/i915_trace.h:788:
+	       TP_STRUCT__entry(

-:156: ERROR:CODE_INDENT: code indent should use tabs where possible
#156: FILE: drivers/gpu/drm/i915/i915_trace.h:789:
+^I^I^I        __field(u32, dev)$

-:157: ERROR:CODE_INDENT: code indent should use tabs where possible
#157: FILE: drivers/gpu/drm/i915/i915_trace.h:790:
+^I^I^I        __field(u16, class)$

-:158: ERROR:CODE_INDENT: code indent should use tabs where possible
#158: FILE: drivers/gpu/drm/i915/i915_trace.h:791:
+^I^I^I        __field(u16, instance)$

-:159: ERROR:CODE_INDENT: code indent should use tabs where possible
#159: FILE: drivers/gpu/drm/i915/i915_trace.h:792:
+^I^I^I        __field(u32, seqno)$

-:160: ERROR:CODE_INDENT: code indent should use tabs where possible
#160: FILE: drivers/gpu/drm/i915/i915_trace.h:793:
+^I^I^I        __field(bool, waiters)$

-:161: ERROR:CODE_INDENT: code indent should use tabs where possible
#161: FILE: drivers/gpu/drm/i915/i915_trace.h:794:
+^I^I^I        ),$

-:163: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#163: FILE: drivers/gpu/drm/i915/i915_trace.h:796:
+	       TP_fast_assign(

-:181: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#181: 
new file mode 100644

-:292: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#292: FILE: drivers/gpu/drm/i915/i915_tracing.h:1:
+// SPDX-License-Identifier: GPL-2.0

total: 6 errors, 2 warnings, 2 checks, 244 lines checked

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

  parent reply	other threads:[~2018-08-09  9:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 15:14 [PATCH v2] drm/i915/tracing: Enable user interrupts while intel_engine_notify is active Tvrtko Ursulin
2018-08-08 15:20 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-08-08 15:34 ` [PATCH v2] " Chris Wilson
2018-08-09  9:07   ` [PATCH v3] " Tvrtko Ursulin
2018-08-09  9:09     ` Tvrtko Ursulin
2018-08-09  9:22     ` Chris Wilson
2018-08-09  9:31       ` Tvrtko Ursulin
2018-08-09 10:01         ` [PATCH v4] " Tvrtko Ursulin
2018-08-09 10:04           ` Chris Wilson
2018-08-09 10:12             ` [PATCH v5] " Tvrtko Ursulin
2018-08-11 22:39           ` [PATCH v4] " kbuild test robot
2018-08-11 22:47           ` kbuild test robot
2018-08-09  9:29 ` Patchwork [this message]
2018-08-09  9:30 ` ✗ Fi.CI.SPARSE: warning for drm/i915/tracing: Enable user interrupts while intel_engine_notify is active (rev2) Patchwork
2018-08-09  9:46 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-09 10:12 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/tracing: Enable user interrupts while intel_engine_notify is active (rev3) Patchwork
2018-08-09 10:13 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-08-09 10:29 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-09 10:33 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/tracing: Enable user interrupts while intel_engine_notify is active (rev4) Patchwork
2018-08-09 10:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-08-09 10:51 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-09 11:41 ` ✓ 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=20180809092930.3702.3430@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    /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