All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: snowball does not compile on linux-next
Date: Mon, 02 Jan 2012 14:55:47 +0100	[thread overview]
Message-ID: <4F01B763.4040201@linaro.org> (raw)
In-Reply-To: <CACRpkdbn6H_s8oC3VdqH2CoCZcPkc+hYccLE1UQJZnqB5eSf3Q@mail.gmail.com>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/02/2012 01:59 PM, Linus Walleij wrote:
> On Mon, Jan 2, 2012 at 12:49 PM, Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>
>> the kernel does not compile when
>> CONFIG_CLKSRC_DBX500_PRCMU_SCHED_CLOCK is set.
>>
>> it fails with :
>>
>> CHK include/linux/version.h CHK
>> include/generated/utsrelease.h make[1]:
>> `include/generated/mach-types.h' is up to date. CALL
>> scripts/checksyscalls.sh CHK include/generated/compile.h CC
>> drivers/clocksource/clksrc-dbx500-prcmu.o
>> drivers/clocksource/clksrc-dbx500-prcmu.c:61: warning: type
>> defaults to ?int? in declaration of ?DEFINE_CLOCK_DATA?
>> drivers/clocksource/clksrc-dbx500-prcmu.c:61: warning: parameter
>> names (without types) in function declaration
>> drivers/clocksource/clksrc-dbx500-prcmu.c: In function
>> ?sched_clock?: drivers/clocksource/clksrc-dbx500-prcmu.c:72:
>> error: implicit declaration of function ?cyc_to_sched_clock?
>> drivers/clocksource/clksrc-dbx500-prcmu.c:72: error: ?cd?
>> undeclared (first use in this function)
>> drivers/clocksource/clksrc-dbx500-prcmu.c:72: error: (Each
>> undeclared identifier is reported only once
>> drivers/clocksource/clksrc-dbx500-prcmu.c:72: error: for each
>> function it appears in.)
>> drivers/clocksource/clksrc-dbx500-prcmu.c: In function
>> ?clksrc_dbx500_prcmu_update_sched_clock?:
>> drivers/clocksource/clksrc-dbx500-prcmu.c:78: error: implicit
>> declaration of function ?update_sched_clock?
>> drivers/clocksource/clksrc-dbx500-prcmu.c:78: error: ?cd?
>> undeclared (first use in this function)
>> drivers/clocksource/clksrc-dbx500-prcmu.c: In function
>> ?clksrc_dbx500_prcmu_init?:
>> drivers/clocksource/clksrc-dbx500-prcmu.c:100: error: implicit
>> declaration of function ?init_sched_clock?
>> drivers/clocksource/clksrc-dbx500-prcmu.c:100: error: ?cd?
>> undeclared (first use in this function) make[2]: ***
>> [drivers/clocksource/clksrc-dbx500-prcmu.o] Error 1 make[1]: ***
>> [drivers/clocksource] Error 2 make[1]: *** Waiting for unfinished
>> jobs.... make: *** [drivers] Error 2 make: *** Waiting for
>> unfinished jobs....
>>
>> Is it dead code ?
>
> No if it was dead it shouldn't get compiled.
>
> It' probably just some fallout from Marc's rewrite of the
> sched_clock() stuff, I'll see if I can cook a patch and send off to
> Marc.

Ok, thanks. I will test the patch you sent.

it seems also the commit :

commit c15def1cc30edeaa74a97205c936be82cdc86df6
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Thu Dec 15 13:38:40 2011 +0100

    ARM: ux500: remove support for early silicon revisions
 
    The DB8500 ED (Early Drop) and V1 are only available inside of
    ST-Ericsson or partners, we have actively replaced and scrapped
    these prototypes. All Nova products on the open market (such as
    the Snowball board) are based on V2 and later ASIC variants.
    So let us focus on supporting the silicon that will be used and
    delete this to get a clear overview.
 
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

removed the U8500_PRCMU_TCDM_BASE_V1 macro definition but it is still
used in drivers/mfd/db8500-prcmu.c

The compilation fails with:

drivers/mfd/db8500-prcmu.c: In function ?db8500_prcmu_early_init?:
drivers/mfd/db8500-prcmu.c:2107: error: ?U8500_PRCMU_TCDM_BASE_V1?
undeclared (first use in this function)
drivers/mfd/db8500-prcmu.c:2107: error: (Each undeclared identifier is
reported only once
drivers/mfd/db8500-prcmu.c:2107: error: for each function it appears in.)
make[2]: *** [drivers/mfd/db8500-prcmu.o] Error 1
make[1]: *** [drivers/mfd] Error 2
make[1]: *** Waiting for unfinished jobs....


- -- 

 <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPAbdjAAoJEAKBbMCpUGYAsBMH/34gi4X+ASaKC8CbJuXe1xHE
7Vp3SRctP+yNQdd4iI3ma9pDnOX9kLl2iuCty3aRy4rpH+hnzHkgKdmfKKRGzH32
FoffLeEIfnGYcC5T+PDO3wL0T1zim33Umo/wyl/CLrHrgV/dX7C1lqLwQ5TF6GI8
g9pQa7raPgNvRNv3gI8p/ult8dvJEplJkl+R3MXUddfCAn4wfL+y4xpliyOwMHhb
uw3ReHAsibmJe1eBD0qh+MvioDuxnHxTLek2eq+eZRUCoiT1gN24L51IGZjbrUlE
zgEW4O0+/Gok4vm7ZYHe1gVqvbkPtMx34mPkf4nCV6QhTihWi1Rq2J6CwqugLhE=
=xA0Z
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-01-02 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 11:49 snowball does not compile on linux-next Daniel Lezcano
2012-01-02 12:59 ` Linus Walleij
2012-01-02 13:55   ` Daniel Lezcano [this message]
2012-01-02 14:00     ` Linus Walleij
2012-01-02 14:00     ` Daniel Lezcano
2012-01-02 15:25   ` Christian Robottom Reis
2012-01-03  7:19     ` Linus Walleij
2012-01-03 13:20       ` Christian Robottom Reis
2012-01-04  9:44         ` Linus Walleij

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=4F01B763.4040201@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --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 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.