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: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Measure CS_TIMESTAMP (rev2)
Date: Mon, 18 May 2020 08:16:16 -0000	[thread overview]
Message-ID: <158978977662.31685.14020453489672942470@emeril.freedesktop.org> (raw)
In-Reply-To: <20200516132444.24007-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915/selftests: Measure CS_TIMESTAMP (rev2)
URL   : https://patchwork.freedesktop.org/series/77320/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
07967d1266af drm/i915/selftests: Measure CS_TIMESTAMP
-:67: CHECK:USLEEP_RANGE: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.rst
#67: FILE: drivers/gpu/drm/i915/gt/selftest_gt_pm.c:52:
+		udelay(1000);

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

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

  parent reply	other threads:[~2020-05-18  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 13:24 [Intel-gfx] [PATCH] drm/i915/selftests: Measure CS_TIMESTAMP Chris Wilson
2020-05-16 13:31 ` Chris Wilson
2020-05-18  9:18   ` Chris Wilson
2020-05-19 10:42   ` Ville Syrjälä
2020-05-19 10:46     ` Chris Wilson
2020-05-19 11:47       ` Ville Syrjälä
2020-05-18  8:16 ` Patchwork [this message]
2020-05-18  8:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/selftests: Measure CS_TIMESTAMP (rev2) Patchwork
2020-05-19 12:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Measure CS_TIMESTAMP (rev3) Patchwork
2020-05-19 12:59 ` [Intel-gfx] ✗ 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=158978977662.31685.14020453489672942470@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.