From: Stephen Rothwell <sfr@canb.auug.org.au> To: Dave Airlie <airlied@linux.ie>, Daniel Vetter <daniel.vetter@ffwll.ch>, Intel Graphics <intel-gfx@lists.freedesktop.org>, DRI <dri-devel@lists.freedesktop.org> Cc: Jani Nikula <jani.nikula@intel.com>, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: linux-next: build failure after merge of the drm tree Date: Mon, 20 Mar 2017 11:51:28 +1100 Message-ID: <20170320115128.0bc3861b@canb.auug.org.au> (raw) Hi Dave, After merging the drm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/i915/i915_irq.c: In function 'gen6_rps_reset_ei': drivers/gpu/drm/i915/i915_irq.c:1115:38: error: 'struct intel_gen6_power_mgmt' has no member named 'down_ei' vlv_c0_read(dev_priv, &dev_priv->rps.down_ei); ^ drivers/gpu/drm/i915/i915_irq.c:1116:15: error: 'struct intel_gen6_power_mgmt' has no member named 'up_ei' dev_priv->rps.up_ei = dev_priv->rps.down_ei; ^ drivers/gpu/drm/i915/i915_irq.c:1116:37: error: 'struct intel_gen6_power_mgmt' has no member named 'down_ei' dev_priv->rps.up_ei = dev_priv->rps.down_ei; ^ drivers/gpu/drm/i915/i915_irq.c: In function 'vlv_wa_c0_ei': drivers/gpu/drm/i915/i915_irq.c:1133:21: error: 'struct intel_gen6_power_mgmt' has no member named 'down_ei' &dev_priv->rps.down_ei, &now, ^ drivers/gpu/drm/i915/i915_irq.c:1136:16: error: 'struct intel_gen6_power_mgmt' has no member named 'down_ei' dev_priv->rps.down_ei = now; ^ drivers/gpu/drm/i915/i915_irq.c:1141:20: error: 'struct intel_gen6_power_mgmt' has no member named 'up_ei' &dev_priv->rps.up_ei, &now, ^ drivers/gpu/drm/i915/i915_irq.c:1144:16: error: 'struct intel_gen6_power_mgmt' has no member named 'up_ei' dev_priv->rps.up_ei = now; ^ Caused by commit 8f68d591d476 ("drm/i915: Stop using RP_DOWN_EI on Baytrail") from the drm-intel-fixes tree and a bad merge resolution on my part. I reapplied that commit by hand. It would be nice if this conflict was resolved in the drm tree. This cherry picking of fixes from new development back to Linus' tree can be a real pain when so many other changes happen in the same files. -- Cheers, Stephen Rothwell _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply index Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-20 0:51 Stephen Rothwell [this message] 2017-03-20 8:03 ` Daniel Vetter 2017-03-20 8:05 ` Daniel Vetter -- strict thread matches above, loose matches on Subject: below -- 2019-11-05 2:54 Stephen Rothwell 2019-10-10 0:22 Stephen Rothwell 2019-07-08 4:48 Stephen Rothwell 2019-04-26 2:17 Stephen Rothwell 2018-05-16 6:53 Stephen Rothwell 2018-05-16 8:09 ` Oded Gabbay 2018-05-17 5:00 ` Dave Airlie 2018-03-13 5:46 Stephen Rothwell 2018-01-02 1:48 Stephen Rothwell 2017-09-28 4:57 Stephen Rothwell 2017-02-23 23:25 Stephen Rothwell 2017-01-24 1:25 Stephen Rothwell 2017-01-25 10:52 ` Vincent ABRIOU 2016-07-15 3:40 Stephen Rothwell 2016-07-15 4:32 ` Sedat Dilek 2016-04-28 1:57 Stephen Rothwell 2016-04-28 8:11 ` Jani Nikula 2016-03-17 4:41 Stephen Rothwell 2016-03-17 8:41 ` Christian König 2016-02-22 0:45 Stephen Rothwell 2015-12-31 10:31 Stephen Rothwell 2016-01-07 2:44 ` Stephen Rothwell 2016-01-11 22:54 ` Stephen Rothwell 2016-01-12 0:31 ` Dave Airlie 2016-01-12 4:35 ` Stephen Rothwell 2016-01-12 7:48 ` Zhu, Rex 2015-12-31 2:40 Stephen Rothwell 2015-12-31 5:14 ` Mark yao 2015-11-04 9:22 Stephen Rothwell 2015-11-09 16:45 ` Guenter Roeck 2015-11-10 4:55 ` Alexandre Courbot 2015-10-06 1:09 Stephen Rothwell 2015-06-09 13:42 Stephen Rothwell 2015-06-09 14:02 ` Deucher, Alexander 2015-06-10 0:28 ` Stephen Rothwell 2015-05-20 3:08 Stephen Rothwell 2015-05-20 4:41 ` Dave Airlie 2015-05-20 5:25 ` Stephen Rothwell 2015-05-20 5:31 ` Stephen Rothwell 2015-05-20 6:01 ` Oded Gabbay 2015-05-20 6:08 ` Dave Airlie 2015-01-29 2:38 Stephen Rothwell 2015-01-29 8:21 ` Oded Gabbay 2015-01-29 9:35 ` Stephen Rothwell 2014-09-08 4:26 Stephen Rothwell 2014-06-05 4:12 Stephen Rothwell 2014-06-05 4:28 ` Stephen Rothwell 2012-09-24 3:18 Stephen Rothwell 2012-09-24 11:31 ` Daniel Vetter 2012-09-24 11:58 ` Stephen Rothwell 2012-08-24 3:49 Stephen Rothwell 2012-05-17 3:47 Stephen Rothwell 2012-04-30 3:22 Stephen Rothwell 2012-04-23 3:42 Stephen Rothwell 2012-03-16 2:53 Stephen Rothwell 2012-03-19 2:45 ` Stephen Rothwell 2011-11-28 2:49 Stephen Rothwell 2011-11-16 0:30 Stephen Rothwell 2011-11-16 10:16 ` Alan Cox 2011-11-16 16:42 ` Jesse Barnes 2011-11-25 1:49 ` Stephen Rothwell 2011-11-25 10:30 ` Alan Cox 2011-11-25 10:34 ` Dave Airlie 2011-11-28 2:53 ` Stephen Rothwell 2011-11-28 11:30 ` Alan Cox 2011-11-28 13:13 ` Stephen Rothwell 2011-11-28 13:18 ` Alan Cox 2011-11-28 13:53 ` Stephen Rothwell 2011-11-28 14:05 ` Dave Airlie 2011-11-28 14:08 ` Alan Cox 2011-11-28 2:52 ` Stephen Rothwell 2011-11-28 5:07 ` Greg KH 2011-11-28 11:33 ` Alan Cox 2011-03-15 3:49 Stephen Rothwell 2010-04-08 3:12 Stephen Rothwell 2010-04-08 3:52 ` Dave Airlie 2010-04-08 4:14 ` Stephen Rothwell 2010-04-08 16:19 ` Tony Luck 2010-04-08 20:50 ` Pauli Nieminen
Reply instructions: You may reply publically 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=20170320115128.0bc3861b@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=airlied@linux.ie \ --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
Linux-Next Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \ linux-next@vger.kernel.org public-inbox-index linux-next Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next AGPL code for this site: git clone https://public-inbox.org/public-inbox.git