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 series starting with [CI,1/2] drm/i915/perf: Wean ourselves off dev_priv
Date: Mon, 07 Oct 2019 15:10:25 -0000 [thread overview]
Message-ID: <20191007151025.14086.91212@emeril.freedesktop.org> (raw)
In-Reply-To: <20191007140812.10963-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/perf: Wean ourselves off dev_priv
URL : https://patchwork.freedesktop.org/series/67689/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c449e123f41b drm/i915/perf: Wean ourselves off dev_priv
-:415: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#415: FILE: drivers/gpu/drm/i915/i915_perf.c:1340:
+ BUG_ON(stream != perf->exclusive_stream);
total: 0 errors, 1 warnings, 0 checks, 1846 lines checked
932d16e56d32 drm/i915/perf: Set the exclusive stream under perf->lock
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-07 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 14:08 [CI 1/2] drm/i915/perf: Wean ourselves off dev_priv Chris Wilson
2019-10-07 14:08 ` [CI 2/2] drm/i915/perf: Set the exclusive stream under perf->lock Chris Wilson
2019-10-07 15:10 ` Patchwork [this message]
2019-10-07 15:34 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915/perf: Wean ourselves off dev_priv Patchwork
2019-10-07 20:42 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-10-07 21:09 [CI 1/2] " Chris Wilson
2019-10-07 22:20 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/2] " 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=20191007151025.14086.91212@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.