Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/5] drm/i915: Don't declare unnecessary shadowing variable
Date: Mon,  3 Mar 2014 17:31:45 +0000	[thread overview]
Message-ID: <1393867908-4604-3-git-send-email-damien.lespiau@intel.com> (raw)
In-Reply-To: <1393867908-4604-1-git-send-email-damien.lespiau@intel.com>

'i' is already defined in the function scope and used elsewhere. Let's
use it instead.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
---
 drivers/gpu/drm/i915/i915_debugfs.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
index d90a707..d247926 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -602,7 +602,6 @@ static int i915_interrupt_info(struct seq_file *m, void *data)
 	intel_runtime_pm_get(dev_priv);
 
 	if (INTEL_INFO(dev)->gen >= 8) {
-		int i;
 		seq_printf(m, "Master Interrupt Control:\t%08x\n",
 			   I915_READ(GEN8_MASTER_IRQ));
 
-- 
1.8.3.1

  parent reply	other threads:[~2014-03-03 17:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 17:31 [PATCH 0/5] Make num_sprites a per pipe value (v3) Damien Lespiau
2014-03-03 17:31 ` [PATCH 1/5] drm/i915: Use a pipe variable to cycle through the pipes Damien Lespiau
2014-03-03 17:31 ` Damien Lespiau [this message]
2014-03-03 17:31 ` [PATCH 3/5] drm/i915: Replace a few for_each_pipe(i) by for_each_pipe(pipe) Damien Lespiau
2014-03-03 17:31 ` [PATCH 4/5] drm/i915: Add a for_each_sprite() macro Damien Lespiau
2014-03-03 17:31 ` [PATCH 5/5] drm/i915: Make num_sprites a per-pipe value Damien Lespiau
2014-03-03 21:16 ` [PATCH 0/5] Make num_sprites a per pipe value (v3) Chris Wilson
2014-03-05 17:48   ` Daniel Vetter

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=1393867908-4604-3-git-send-email-damien.lespiau@intel.com \
    --to=damien.lespiau@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