linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: vexpress issues in next-20121029
Date: Mon, 5 Nov 2012 09:35:32 +0000	[thread overview]
Message-ID: <20121105093532.GC28327@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1351613819.6199.14.camel@hornet>

On Tue, Oct 30, 2012 at 04:16:59PM +0000, Pawel Moll wrote:
> Hi Stephen,
> 
> On Mon, 2012-10-29 at 20:24 +0000, Stephen Warren wrote:
> > 1) At compile-time: v2m_timer_init() and v2m_dt_timer_init() reference
> > functions vexpress_clk_init() and vexpress_clk_of_init() respectively,
> > which don't appear anywhere in the source tree.
> 
> There was a glitch between clk-next and arm-soc - it should be fine
> starting with next-20121030.

The problem is still there - my builds of my tree plus arm-soc are
continuing to fail with:

arch/arm/mach-vexpress/built-in.o: In function `v2m_timer_init':
reset.c:(.init.text+0xe0): undefined reference to `vexpress_clk_init'
arch/arm/mach-vexpress/built-in.o: In function `v2m_dt_timer_init':
reset.c:(.init.text+0x114): undefined reference to `vexpress_clk_of_init'

My guess is you have a dependency between the clk-next tree and arm-soc
which you haven't told the arm-soc people about.

  reply	other threads:[~2012-11-05  9:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 20:24 vexpress issues in next-20121029 Stephen Warren
2012-10-30 16:16 ` Pawel Moll
2012-11-05  9:35   ` Russell King - ARM Linux [this message]
2012-11-05  9:45     ` Russell King - ARM Linux
2012-11-05 14:43       ` Pawel Moll
2012-11-05 16:47         ` Arnd Bergmann
2012-11-05 17:19           ` Pawel Moll
2012-11-05 17:52             ` Arnd Bergmann
2012-11-05 18:12               ` Pawel Moll
2012-11-07 20:36 ` Stephen Warren
2012-11-08 18:54   ` Pawel Moll

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=20121105093532.GC28327@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).