From: Patchwork <patchwork@emeril.freedesktop.org>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/perf: Refactor oa object to better manage resources (rev3)
Date: Wed, 15 May 2019 18:17:36 -0000 [thread overview]
Message-ID: <20190515181736.5991.41951@emeril.freedesktop.org> (raw)
In-Reply-To: <20190515180736.3425-1-umesh.nerlige.ramappa@intel.com>
== Series Details ==
Series: drm/i915/perf: Refactor oa object to better manage resources (rev3)
URL : https://patchwork.freedesktop.org/series/60176/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3c6e6cc91331 drm/i915/perf: Refactor oa object to better manage resources
-:1522: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#1522: FILE: drivers/gpu/drm/i915/i915_perf.c:1366:
+ BUG_ON(stream != dev_priv->perf.exclusive_stream);
total: 0 errors, 1 warnings, 0 checks, 2166 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-05-15 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 18:07 [PATCH] drm/i915/perf: Refactor oa object to better manage resources Umesh Nerlige Ramappa
2019-05-15 18:17 ` Patchwork [this message]
2019-05-15 18:18 ` ✗ Fi.CI.SPARSE: warning for drm/i915/perf: Refactor oa object to better manage resources (rev3) Patchwork
2019-05-15 18:43 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-16 0:29 ` ✓ Fi.CI.IGT: " Patchwork
2019-05-16 9:48 ` [PATCH] drm/i915/perf: Refactor oa object to better manage resources Lionel Landwerlin
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=20190515181736.5991.41951@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@intel.com \
/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.