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: Mark live_forcewake_ops as unreliable
Date: Sun, 07 Apr 2019 19:27:29 -0000 [thread overview]
Message-ID: <20190407192729.1804.14612@emeril.freedesktop.org> (raw)
In-Reply-To: <20190407191924.14554-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/selftests: Mark live_forcewake_ops as unreliable
URL : https://patchwork.freedesktop.org/series/59129/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
2c9755fcbe03 drm/i915/selftests: Mark live_forcewake_ops as unreliable
-:8: WARNING:TYPO_SPELLING: 'interferring' may be misspelled - perhaps 'interfering'?
#8:
interferring with the powerwells, or the powerwell doesn't quite behave
-:31: WARNING:TYPO_SPELLING: 'interferring' may be misspelled - perhaps 'interfering'?
#31: FILE: drivers/gpu/drm/i915/selftests/intel_uncore.c:162:
+ * external parties interferring with the powerwells.
total: 0 errors, 2 warnings, 0 checks, 15 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-04-07 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 19:19 [PATCH] drm/i915/selftests: Mark live_forcewake_ops as unreliable Chris Wilson
2019-04-07 19:26 ` Chris Wilson
2019-04-08 17:24 ` Daniele Ceraolo Spurio
2019-04-07 19:27 ` Patchwork [this message]
2019-04-07 19:46 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-04-07 19:49 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Mark live_forcewake_ops as unreliable (rev2) Patchwork
2019-04-07 20:08 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-07 21:21 ` ✓ 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=20190407192729.1804.14612@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox