From: Nischal Varide <nischal.varide@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Nischal Varide <nischal.varide@intel.com>
Subject: [Intel-gfx] [PATCH 8/8] Critical KlockWork Error - Fixes - intel_combo_phy.c Uninitialized Variable-1
Date: Fri, 14 Aug 2020 08:19:50 +0530 [thread overview]
Message-ID: <20200814024950.26830-8-nischal.varide@intel.com> (raw)
In-Reply-To: <20200814024950.26830-1-nischal.varide@intel.com>
---
drivers/gpu/drm/i915/display/intel_combo_phy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_combo_phy.c b/drivers/gpu/drm/i915/display/intel_combo_phy.c
index eccaa79cb4a9..6e721b8ed611 100644
--- a/drivers/gpu/drm/i915/display/intel_combo_phy.c
+++ b/drivers/gpu/drm/i915/display/intel_combo_phy.c
@@ -258,7 +258,7 @@ static bool phy_is_master(struct drm_i915_private *dev_priv, enum phy phy)
static bool icl_combo_phy_verify_state(struct drm_i915_private *dev_priv,
enum phy phy)
{
- bool ret;
+ bool ret = 1;
u32 expected_val = 0;
if (!icl_combo_phy_enabled(dev_priv, phy))
--
2.26.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-08-14 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 2:49 [Intel-gfx] [PATCH 1/8] Critical KlockWork Error - Fixes - intel_cdclk.c - Possible NullPointerDereference1 Nischal Varide
2020-08-14 2:49 ` [Intel-gfx] [PATCH 2/8] Critical KlockWork Error - Fixes - intel_atomic.c " Nischal Varide
2020-08-14 2:49 ` [Intel-gfx] [PATCH 3/8] Critical KlockWork Error - Fixes - intel_fbdev.c " Nischal Varide
2020-08-14 2:49 ` [Intel-gfx] [PATCH 4/8] Critical KlockWork Error - Fixes - intel_display.c " Nischal Varide
2020-08-14 2:49 ` [Intel-gfx] [PATCH 5/8] Critical KlockWork Error - Fixes - intel_sdvo.c " Nischal Varide
2020-08-14 2:49 ` [Intel-gfx] [PATCH 6/8] Critical KlockWork Error - Fixes - intel_tv.c " Nischal Varide
2020-08-14 2:49 ` [Intel-gfx] [PATCH 7/8] Critical KlockWork Error - Fixes - intel_display_power.c - Possible NullPointerDereference2 Nischal Varide
2020-08-14 2:49 ` Nischal Varide [this message]
2020-08-14 13:33 ` [Intel-gfx] [PATCH 8/8] Critical KlockWork Error - Fixes - intel_combo_phy.c Uninitialized Variable-1 Anshuman Gupta
2020-08-14 10:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] Critical KlockWork Error - Fixes - intel_cdclk.c - Possible NullPointerDereference1 Patchwork
2020-08-14 13:35 ` Shankar, Uma
2020-08-14 10:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-08-14 10:36 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-08-14 13:39 ` [Intel-gfx] [PATCH 1/8] " Shankar, Uma
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=20200814024950.26830-8-nischal.varide@intel.com \
--to=nischal.varide@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.