From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 0/5] drm/i915: some BUG_ON() removals
Date: Fri, 26 Aug 2022 11:38:12 +0300 [thread overview]
Message-ID: <cover.1661503049.git.jani.nikula@intel.com> (raw)
Avoid BUG_ON(). Remove some of the low-hanging fruit.
Jani Nikula (5):
drm/i915/crt: replace BUG_ON() with drm_WARN_ON()
drm/i915/dpll: replace BUG_ON() with drm_WARN_ON()
drm/i915/pch: replace BUG_ON() with drm_WARN_ON()
drm/i915/perf: replace BUG_ON() with WARN_ON()
drm/i915/fence: replace BUG_ON() with BUILD_BUG_ON()
drivers/gpu/drm/i915/display/intel_crt.c | 3 ++-
drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 6 ++++--
drivers/gpu/drm/i915/display/intel_pch_refclk.c | 2 +-
drivers/gpu/drm/i915/i915_perf.c | 3 ++-
drivers/gpu/drm/i915/i915_sw_fence.c | 2 --
drivers/gpu/drm/i915/i915_sw_fence.h | 6 +++++-
6 files changed, 14 insertions(+), 8 deletions(-)
--
2.34.1
next reply other threads:[~2022-08-26 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 8:38 Jani Nikula [this message]
2022-08-26 8:38 ` [Intel-gfx] [PATCH 1/5] drm/i915/crt: replace BUG_ON() with drm_WARN_ON() Jani Nikula
2022-08-26 10:59 ` Ville Syrjälä
2022-08-26 8:38 ` [Intel-gfx] [PATCH 2/5] drm/i915/dpll: " Jani Nikula
2022-08-26 11:08 ` Ville Syrjälä
2022-08-26 8:38 ` [Intel-gfx] [PATCH 3/5] drm/i915/pch: " Jani Nikula
2022-08-26 8:38 ` [Intel-gfx] [PATCH 4/5] drm/i915/perf: replace BUG_ON() with WARN_ON() Jani Nikula
2022-08-26 8:38 ` [Intel-gfx] [PATCH 5/5] drm/i915/fence: replace BUG_ON() with BUILD_BUG_ON() Jani Nikula
2022-08-26 10:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: some BUG_ON() removals Patchwork
2022-08-26 10:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-30 11:24 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=cover.1661503049.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--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.