From: Stephen Rothwell <sfr@canb.auug.org.au> To: Daniel Vetter <daniel.vetter@ffwll.ch>, <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org> Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: linux-next: build failure after merge of the drm-intel tree Date: Fri, 15 Feb 2013 13:37:14 +1100 [thread overview] Message-ID: <20130215133714.6f55139ad1a037b7b9fa1b70@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 291 bytes --] Hi all, After merging the drm-intel tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "pm_vt_switch_unregister" [drivers/video/fb.ko] undefined! I have dropped the tree for today. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au [-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au> To: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: linux-next: build failure after merge of the drm-intel tree Date: Fri, 15 Feb 2013 13:37:14 +1100 [thread overview] Message-ID: <20130215133714.6f55139ad1a037b7b9fa1b70@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 291 bytes --] Hi all, After merging the drm-intel tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "pm_vt_switch_unregister" [drivers/video/fb.ko] undefined! I have dropped the tree for today. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au [-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-02-15 2:37 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-15 2:37 Stephen Rothwell [this message] 2013-02-15 2:37 ` linux-next: build failure after merge of the drm-intel tree Stephen Rothwell 2013-02-15 9:30 ` Daniel Vetter 2013-02-15 9:30 ` Daniel Vetter 2013-02-15 16:16 ` Jesse Barnes 2013-02-19 2:01 ` Stephen Rothwell 2013-02-19 10:28 ` Daniel Vetter 2014-03-19 0:53 Stephen Rothwell 2014-03-19 0:53 ` Stephen Rothwell 2014-03-19 1:18 ` Steven Rostedt 2014-03-19 1:18 ` Steven Rostedt 2014-04-03 1:24 Stephen Rothwell 2014-04-03 1:24 ` Stephen Rothwell 2016-05-23 2:24 Stephen Rothwell 2016-05-23 2:24 ` Stephen Rothwell 2016-08-23 1:56 Stephen Rothwell 2016-08-23 1:56 ` Stephen Rothwell 2016-08-23 16:33 ` Daniel Vetter 2016-08-23 16:33 ` Daniel Vetter 2016-10-17 23:59 Stephen Rothwell 2016-10-18 6:26 ` Daniel Vetter 2018-05-08 1:07 Stephen Rothwell 2018-05-08 7:08 ` Oleksandr Andrushchenko 2018-05-08 7:08 ` Oleksandr Andrushchenko 2018-05-09 5:02 ` Stephen Rothwell 2018-05-09 5:02 ` Stephen Rothwell 2018-05-09 5:08 ` Christoph Hellwig 2018-05-09 5:18 ` Stephen Rothwell 2018-07-13 1:54 Stephen Rothwell 2018-07-23 2:29 ` Stephen Rothwell 2019-03-27 2:59 Stephen Rothwell 2019-03-27 2:59 ` Stephen Rothwell 2019-03-27 11:07 ` Joonas Lahtinen 2019-03-27 11:07 ` Joonas Lahtinen 2019-03-27 11:31 ` Stephen Rothwell 2019-03-27 11:31 ` Stephen Rothwell 2019-12-09 22:39 Stephen Rothwell 2019-12-09 22:42 ` Stephen Rothwell 2019-12-11 9:31 ` Jani Nikula 2019-12-11 9:31 ` Jani Nikula 2021-01-19 23:57 Stephen Rothwell 2021-01-19 23:57 ` Stephen Rothwell 2021-01-21 1:11 ` Stephen Rothwell 2021-01-21 1:11 ` Stephen Rothwell 2021-05-21 1:58 Stephen Rothwell 2021-05-21 1:58 ` Stephen Rothwell 2022-02-15 1:10 Stephen Rothwell 2022-02-15 1:10 ` Stephen Rothwell 2022-02-15 12:11 ` Jani Nikula 2022-02-15 12:11 ` Jani Nikula 2022-04-26 2:08 Stephen Rothwell 2022-04-26 2:08 ` Stephen Rothwell 2022-04-26 7:36 ` Jani Nikula 2022-04-26 7:36 ` Jani Nikula 2022-08-26 2:36 Stephen Rothwell 2022-08-26 2:36 ` Stephen Rothwell 2022-08-26 7:50 ` Jani Nikula 2022-08-26 7:50 ` Jani Nikula
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=20130215133714.6f55139ad1a037b7b9fa1b70@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=daniel.vetter@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --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: linkBe 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.