From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [drm-intel:drm-intel-nightly 30/30] drivers/gpu/drm/i915/intel_pm.c:3445:2: error:
Date: Tue, 09 Oct 2012 23:22:52 +0000 [thread overview]
Message-ID: <20121009232252.GB8107@localhost> (raw)
Hi Daniel,
FYI, kernel build failed on
tree: git://people.freedesktop.org/~danvet/drm-intel.git drm-intel-nightly
head: 90adfd05fd3bd8c970bde7de4db0e4b5b9642725
commit: 90adfd05fd3bd8c970bde7de4db0e4b5b9642725 [30/30] Merge remote-tracking branch 'origin/drm-intel-fixes' into drm-intel-nightly
config: x86_64-allmodconfig
All error/warnings:
drivers/gpu/drm/i915/intel_pm.c: In function 'gen6_init_clock_gating':
drivers/gpu/drm/i915/intel_pm.c:3445:2: error: '_3D_CHICKEN3_SF_DISABLE_FASTCLIP_CULL' undeclared (first use in this function)
drivers/gpu/drm/i915/intel_pm.c:3445:2: note: each undeclared identifier is reported only once for each function it appears in
vim +3445 drivers/gpu/drm/i915/intel_pm.c
6f1d69b0 Eugeni Dodonov 2012-04-18 3439 I915_WRITE(GEN6_UCGCTL2,
0f846f81 Jesse Barnes 2012-06-14 3440 GEN7_VDSUNIT_CLOCK_GATE_DISABLE |
6f1d69b0 Eugeni Dodonov 2012-04-18 3441 GEN6_RCPBUNIT_CLOCK_GATE_DISABLE |
6f1d69b0 Eugeni Dodonov 2012-04-18 3442 GEN6_RCCUNIT_CLOCK_GATE_DISABLE);
6f1d69b0 Eugeni Dodonov 2012-04-18 3443
6f1d69b0 Eugeni Dodonov 2012-04-18 3444 /* Bspec says we need to always set all mask bits. */
c8f1e7e2 Kenneth Graunke 2012-10-07 @3445 I915_WRITE(_3D_CHICKEN3, (0xFFFF << 16) |
c8f1e7e2 Kenneth Graunke 2012-10-07 3446 _3D_CHICKEN3_SF_DISABLE_FASTCLIP_CULL);
6f1d69b0 Eugeni Dodonov 2012-04-18 3447
6f1d69b0 Eugeni Dodonov 2012-04-18 3448 /*
The code at line 3445 was first introduced by commit:
c8f1e7e drm/i915: Set guardband clipping workaround bit in the right register.
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-10-09 23:22 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=20121009232252.GB8107@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox