All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: OMAP* Latest build failures
Date: Wed, 14 Nov 2012 09:26:43 +0000	[thread overview]
Message-ID: <20121114092643.GG3290@n2100.arm.linux.org.uk> (raw)

OMAP* allnoconfig fails:

arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
twl-common.c:(.text+0x1e08): undefined reference to `omap_pm_set_min_bus_tput'
arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_init_postsetup':
twl-common.c:(.init.text+0x8f8): undefined reference to `omap_pm_if_early_init'
arch/arm/mach-omap2/built-in.o: In function `omap_serial_init_port':
twl-common.c:(.init.text+0x1284): undefined reference to `omap_pm_get_dev_context_loss_count'
arch/arm/mach-omap2/built-in.o: In function `omap_timer_init':
twl-common.c:(.init.text+0x1544): undefined reference to `omap_pm_get_dev_context_loss_count'
arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_init':
twl-common.c:(.init.text+0x1af0): undefined reference to `omap_pm_if_init'
arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
twl-common.c:(.init.text+0x2168): undefined reference to `omap_pm_get_dev_context_loss_count'
arch/arm/mach-omap2/built-in.o: In function `omap_display_init':
twl-common.c:(.init.text+0x25cc): undefined reference to `omap_pm_get_dev_context_loss_count'

OMAP4 randconfig fails:

arch/arm/mach-omap2/cm_common.c: In function 'cm_register':
arch/arm/mach-omap2/cm_common.c:42:11: error: 'EINVAL' undeclared (first use in this function)
arch/arm/mach-omap2/cm_common.c:45:11: error: 'EEXIST' undeclared (first use in this function)
arch/arm/mach-omap2/cm_common.c: In function 'cm_unregister':
arch/arm/mach-omap2/cm_common.c:66:11: error: 'EINVAL' undeclared (first use in this function)

You know where to find the build information and results...

WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP* Latest build failures
Date: Wed, 14 Nov 2012 09:26:43 +0000	[thread overview]
Message-ID: <20121114092643.GG3290@n2100.arm.linux.org.uk> (raw)

OMAP* allnoconfig fails:

arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
twl-common.c:(.text+0x1e08): undefined reference to `omap_pm_set_min_bus_tput'
arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_init_postsetup':
twl-common.c:(.init.text+0x8f8): undefined reference to `omap_pm_if_early_init'
arch/arm/mach-omap2/built-in.o: In function `omap_serial_init_port':
twl-common.c:(.init.text+0x1284): undefined reference to `omap_pm_get_dev_context_loss_count'
arch/arm/mach-omap2/built-in.o: In function `omap_timer_init':
twl-common.c:(.init.text+0x1544): undefined reference to `omap_pm_get_dev_context_loss_count'
arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_init':
twl-common.c:(.init.text+0x1af0): undefined reference to `omap_pm_if_init'
arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
twl-common.c:(.init.text+0x2168): undefined reference to `omap_pm_get_dev_context_loss_count'
arch/arm/mach-omap2/built-in.o: In function `omap_display_init':
twl-common.c:(.init.text+0x25cc): undefined reference to `omap_pm_get_dev_context_loss_count'

OMAP4 randconfig fails:

arch/arm/mach-omap2/cm_common.c: In function 'cm_register':
arch/arm/mach-omap2/cm_common.c:42:11: error: 'EINVAL' undeclared (first use in this function)
arch/arm/mach-omap2/cm_common.c:45:11: error: 'EEXIST' undeclared (first use in this function)
arch/arm/mach-omap2/cm_common.c: In function 'cm_unregister':
arch/arm/mach-omap2/cm_common.c:66:11: error: 'EINVAL' undeclared (first use in this function)

You know where to find the build information and results...

             reply	other threads:[~2012-11-14  9:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  9:26 Russell King - ARM Linux [this message]
2012-11-14  9:26 ` OMAP* Latest build failures Russell King - ARM Linux
2012-11-14 10:08 ` Peter Ujfalusi
2012-11-14 10:08   ` Peter Ujfalusi
2012-11-14 10:35   ` Russell King - ARM Linux
2012-11-14 10:35     ` Russell King - ARM Linux
2012-11-14 11:45 ` Tomi Valkeinen
2012-11-14 11:45   ` Tomi Valkeinen
2012-11-14 16:48   ` Tony Lindgren
2012-11-14 16:48     ` Tony Lindgren
2012-11-14 16:59     ` Tony Lindgren
2012-11-14 16:59       ` Tony Lindgren
2012-11-14 17:17       ` Tony Lindgren
2012-11-14 17:17         ` Tony Lindgren
2012-11-14 17:44         ` Russell King - ARM Linux
2012-11-14 17:44           ` Russell King - ARM Linux
2012-11-14 17:42   ` Russell King - ARM Linux
2012-11-14 17:42     ` Russell King - ARM Linux
2012-11-17  9:33 ` Russell King - ARM Linux
2012-11-17  9:33   ` Russell King - ARM Linux
2012-11-20 17:57   ` Tony Lindgren
2012-11-20 17:57     ` Tony Lindgren
2012-11-20 23:00     ` Jon Hunter
2012-11-20 23:00       ` Jon Hunter
2012-11-28 15:18       ` Russell King - ARM Linux
2012-11-28 15:18         ` Russell King - ARM Linux
2012-11-28 21:43         ` Jon Hunter
2012-11-28 21:43           ` Jon Hunter
2012-11-28 14:04     ` Eduardo Valentin
2012-11-28 14:04       ` Eduardo Valentin
2012-11-28 15:16       ` Russell King - ARM Linux
2012-11-28 15:16         ` Russell King - ARM Linux

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=20121114092643.GG3290@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@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 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.