From: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/2] drm/i915: Use int instead of u32 to cache GuC logging level
Date: Tue, 3 Apr 2018 17:04:56 -0700 [thread overview]
Message-ID: <20180404000456.1407-2-radhakrishna.sripada@intel.com> (raw)
In-Reply-To: <20180404000456.1407-1-radhakrishna.sripada@intel.com>
Static code analysis tool has reported an unused check of
log_level<0 when using u32. Use int instead of u32 to store guc_log_level.
Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
Signed-off-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
---
drivers/gpu/drm/i915/intel_guc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_guc.c b/drivers/gpu/drm/i915/intel_guc.c
index a00a59a7d9ec..eb6f0bb7c084 100644
--- a/drivers/gpu/drm/i915/intel_guc.c
+++ b/drivers/gpu/drm/i915/intel_guc.c
@@ -225,7 +225,7 @@ static u32 get_core_family(struct drm_i915_private *dev_priv)
static u32 get_log_control_flags(void)
{
- u32 level = i915_modparams.guc_log_level;
+ int level = i915_modparams.guc_log_level;
u32 flags = 0;
GEM_BUG_ON(level < 0);
--
2.9.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-04-04 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 0:04 [PATCH 1/2] drm/i915: Fix memory leak in intel_hdcp auth Radhakrishna Sripada
2018-04-04 0:04 ` Radhakrishna Sripada [this message]
2018-04-04 0:36 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2018-04-04 1:20 ` ✓ Fi.CI.IGT: " Patchwork
2018-04-04 12:04 ` [PATCH 1/2] " Jani Nikula
2018-04-04 23:05 ` Srivatsa, Anusha
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=20180404000456.1407-2-radhakrishna.sripada@intel.com \
--to=radhakrishna.sripada@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox