All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Jani Nikula <jani.nikula@intel.com>
Subject: linux-next: build warning after merge of the drm-intel-fixes tree
Date: Thu, 8 Jun 2017 10:20:31 +1000	[thread overview]
Message-ID: <20170608102031.456ce4d3@canb.auug.org.au> (raw)

Hi all,

After merging the drm-misc-fixes tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/gpu/drm/i915/intel_engine_cs.c: In function 'intel_engine_is_idle':
drivers/gpu/drm/i915/intel_engine_cs.c:1103:27: warning: unused variable 'dev_priv' [-Wunused-variable]
  struct drm_i915_private *dev_priv = engine->i915;
                           ^

Introduced by commit

  d9533f19d840 ("drm/i915: Hold a wakeref for probing the ring registers")

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2017-06-08  0:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08  0:20 Stephen Rothwell [this message]
2021-03-24 22:24 linux-next: build warning after merge of the drm-intel-fixes tree Stephen Rothwell
2021-03-24 22:24 ` Stephen Rothwell
2021-03-26  8:58 Stephen Rothwell
2021-03-26  8:58 ` Stephen Rothwell
2021-03-28 22:01 ` Stephen Rothwell
2021-03-28 22:01   ` Stephen Rothwell
2021-03-29 18:23   ` Imre Deak
2021-03-29 18:23     ` Imre Deak
2021-04-08 10:38     ` Daniel Vetter
2021-04-08 10:38       ` Daniel Vetter
2021-04-08 15:20       ` Imre Deak
2021-04-08 15:20         ` Imre Deak
2021-07-20  6:32 Stephen Rothwell
2021-07-20  6:32 ` Stephen Rothwell

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=20170608102031.456ce4d3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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.