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: Include priority and completed status in request in/out tracepoints
Date: Fri, 04 May 2018 12:40:47 -0000	[thread overview]
Message-ID: <20180504124047.23927.2480@emeril.freedesktop.org> (raw)
In-Reply-To: <20180504115643.22437-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: drm/i915: Include priority and completed status in request in/out tracepoints
URL   : https://patchwork.freedesktop.org/series/42678/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
0e6962a6d576 drm/i915: Include priority and completed status in request in/out tracepoints
-:57: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#57: FILE: drivers/gpu/drm/i915/i915_trace.h:686:
+	    TP_STRUCT__entry(

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

-:95: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#95: FILE: drivers/gpu/drm/i915/i915_trace.h:718:
+	    TP_STRUCT__entry(

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

total: 0 errors, 0 warnings, 4 checks, 103 lines checked

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

  parent reply	other threads:[~2018-05-04 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 11:56 [PATCH] drm/i915: Include priority and completed status in request in/out tracepoints Tvrtko Ursulin
2018-05-04 12:05 ` Chris Wilson
2018-05-04 12:40 ` Patchwork [this message]
2018-05-04 12:55 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-04 14:12 ` ✓ 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=20180504124047.23927.2480@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