All of 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 drm/i915/selftests: Smoketest preemption
Date: Fri, 21 Sep 2018 10:29:29 -0000	[thread overview]
Message-ID: <20180921102929.19543.83487@emeril.freedesktop.org> (raw)
In-Reply-To: <20180921081122.2206-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915/selftests: Smoketest preemption
URL   : https://patchwork.freedesktop.org/series/50002/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
9badaef7a3f0 drm/i915/selftests: Smoketest preemption
-:50: WARNING:LINE_SPACING: Missing a blank line after declarations
#50: FILE: drivers/gpu/drm/i915/selftests/intel_lrc.c:594:
+	enum intel_engine_id id;
+	IGT_TIMEOUT(end_time);

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

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

  reply	other threads:[~2018-09-21 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21  8:11 [PATCH] drm/i915/selftests: Smoketest preemption Chris Wilson
2018-09-21 10:29 ` Patchwork [this message]
2018-09-21 10:29 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-09-21 10:54 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-21 12:17 ` [PATCH v2] " Chris Wilson
2018-09-21 12:34 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Smoketest preemption (rev2) Patchwork
2018-09-21 12:35 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-09-21 12:59 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-09-21 13:01 ` ✓ Fi.CI.IGT: success for drm/i915/selftests: Smoketest preemption 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=20180921102929.19543.83487@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.