Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org
Subject: Re: [PATCH v2] drm/i915: Show RPS autotuning thresholds along with waitboost
Date: Sun, 14 Aug 2016 21:58:58 +0800	[thread overview]
Message-ID: <201608142143.vaeq4Lfj%fengguang.wu@intel.com> (raw)
In-Reply-To: <1471181336-27523-1-git-send-email-chris@chris-wilson.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]

Hi Chris,

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v4.8-rc1 next-20160812]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Show-RPS-autotuning-thresholds-along-with-waitboost/20160814-213058
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-x009-201633 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/gpu/drm/i915/i915_debugfs.c: In function 'i915_rps_boost_info':
>> drivers/gpu/drm/i915/i915_debugfs.c:2468:44: error: 'struct intel_gen6_power_mgmt' has no member named 'boost_freq'; did you mean 'cur_freq'?
         intel_gpu_freq(dev_priv, dev_priv->rps.boost_freq));
                                               ^

vim +2468 drivers/gpu/drm/i915/i915_debugfs.c

  2462			   intel_gpu_freq(dev_priv, dev_priv->rps.min_freq_softlimit),
  2463			   intel_gpu_freq(dev_priv, dev_priv->rps.max_freq_softlimit),
  2464			   intel_gpu_freq(dev_priv, dev_priv->rps.max_freq));
  2465		seq_printf(m, "  idle:%d, efficient:%d, boost:%d\n",
  2466			   intel_gpu_freq(dev_priv, dev_priv->rps.idle_freq),
  2467			   intel_gpu_freq(dev_priv, dev_priv->rps.efficient_freq),
> 2468			   intel_gpu_freq(dev_priv, dev_priv->rps.boost_freq));
  2469	
  2470		mutex_lock(&dev->filelist_mutex);
  2471		spin_lock(&dev_priv->rps.client_lock);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 27025 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-08-14 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14  8:52 [PATCH] drm/i915: Show RPS autotuning thresholds along with waitboost Chris Wilson
2016-08-14  9:21 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-08-14 13:28 ` [PATCH v2] " Chris Wilson
2016-08-14 13:58   ` kbuild test robot [this message]
2016-08-15  8:27   ` David Weinehall
2016-08-14 13:52 ` ✗ Ro.CI.BAT: failure for drm/i915: Show RPS autotuning thresholds along with waitboost (rev2) Patchwork

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=201608142143.vaeq4Lfj%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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