From: kbuild test robot <fengguang.wu@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
dri-devel@lists.freedesktop.org
Subject: [drm-intel:drm-intel-next-queued 2/2] drivers/gpu/drm/i915/i915_gem_stolen.c:516:20: error: unused variable 'ggtt'
Date: Fri, 18 Nov 2016 03:16:26 +0800 [thread overview]
Message-ID: <201611180323.Ebkl3OIS%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]
tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
head: 95a2e2be952c3c3a643b8e0504f2ceef15294d4d
commit: 95a2e2be952c3c3a643b8e0504f2ceef15294d4d [2/2] drm/i915: Remove stolen object spam
config: x86_64-randconfig-in0-11180217 (attached as .config)
compiler: gcc-4.6 (Debian 4.6.4-7) 4.6.4
reproduce:
git checkout 95a2e2be952c3c3a643b8e0504f2ceef15294d4d
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/i915_gem_stolen.c: In function 'i915_pages_create_for_stolen':
>> drivers/gpu/drm/i915/i915_gem_stolen.c:516:20: error: unused variable 'ggtt' [-Werror=unused-variable]
cc1: all warnings being treated as errors
vim +/ggtt +516 drivers/gpu/drm/i915/i915_gem_stolen.c
0104fdbb8 Chris Wilson 2012-11-15 510
0104fdbb8 Chris Wilson 2012-11-15 511 static struct sg_table *
0104fdbb8 Chris Wilson 2012-11-15 512 i915_pages_create_for_stolen(struct drm_device *dev,
0104fdbb8 Chris Wilson 2012-11-15 513 u32 offset, u32 size)
0104fdbb8 Chris Wilson 2012-11-15 514 {
72e96d645 Joonas Lahtinen 2016-03-30 515 struct drm_i915_private *dev_priv = to_i915(dev);
72e96d645 Joonas Lahtinen 2016-03-30 @516 struct i915_ggtt *ggtt = &dev_priv->ggtt;
0104fdbb8 Chris Wilson 2012-11-15 517 struct sg_table *st;
0104fdbb8 Chris Wilson 2012-11-15 518 struct scatterlist *sg;
0104fdbb8 Chris Wilson 2012-11-15 519
:::::: The code at line 516 was first introduced by commit
:::::: 72e96d6450c067f58b65224bb5e73914e2cc43ab drm/i915: Refer to GGTT {,VM} consistently
:::::: TO: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
:::::: CC: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24666 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2016-11-17 19:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201611180323.Ebkl3OIS%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.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;
as well as URLs for NNTP newsgroup(s).