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 series starting with [CI,1/2] drm/i915: Be wary of data races when reading the active execlists
Date: Thu, 16 Jul 2020 14:31:11 -0000 [thread overview]
Message-ID: <159490987161.25377.9577795759719192540@emeril.freedesktop.org> (raw)
In-Reply-To: <20200716142207.13003-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [CI,1/2] drm/i915: Be wary of data races when reading the active execlists
URL : https://patchwork.freedesktop.org/series/79556/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a9025407e910 drm/i915: Be wary of data races when reading the active execlists
-:92: WARNING:TYPO_SPELLING: 'overwritting' may be misspelled - perhaps 'overwriting'?
#92: FILE: drivers/gpu/drm/i915/i915_request.c:409:
+ * of execlists->pending[] to execlists->inflight[], overwritting
total: 0 errors, 1 warnings, 0 checks, 67 lines checked
b3af951bbc96 drm/i915: Remove i915_request.lock requirement for execution callbacks
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-07-16 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 14:22 [Intel-gfx] [CI 1/2] drm/i915: Be wary of data races when reading the active execlists Chris Wilson
2020-07-16 14:22 ` [Intel-gfx] [CI 2/2] drm/i915: Remove i915_request.lock requirement for execution callbacks Chris Wilson
2020-07-16 14:31 ` Patchwork [this message]
2020-07-16 14:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/2] drm/i915: Be wary of data races when reading the active execlists Patchwork
2020-07-16 14:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-16 17:55 ` [Intel-gfx] ✓ 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=159490987161.25377.9577795759719192540@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.