From: Rob Herring <robherring2@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: DT clock binding support build break
Date: Mon, 16 Jul 2012 14:19:45 +0000 [thread overview]
Message-ID: <50042301.6000108@gmail.com> (raw)
In-Reply-To: <5003F6DF.2010107@nvidia.com>
On 07/16/2012 06:11 AM, Prashant Gaikwad wrote:
> Hi Rob,
>
> DT clock binding support patch breaks build when CONFIG_COMMON_CLK is
> not enabled.
>
> /**
> LD init/built-in.o
> drivers/built-in.o: In function `of_clk_get':
> /home/ldewangan/upstreaming/july09/linux-next/drivers/clk/clkdev.c:42: undefined reference to `of_clk_get_from_provider'
> make: *** [vmlinux] Error 1
> **/
>
> Any solution?
I'll get a fix out today.
Rob
>
> Thanks & Regards,
> Prashant G
WARNING: multiple messages have this Message-ID (diff)
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: DT clock binding support build break
Date: Mon, 16 Jul 2012 09:19:45 -0500 [thread overview]
Message-ID: <50042301.6000108@gmail.com> (raw)
In-Reply-To: <5003F6DF.2010107@nvidia.com>
On 07/16/2012 06:11 AM, Prashant Gaikwad wrote:
> Hi Rob,
>
> DT clock binding support patch breaks build when CONFIG_COMMON_CLK is
> not enabled.
>
> /**
> LD init/built-in.o
> drivers/built-in.o: In function `of_clk_get':
> /home/ldewangan/upstreaming/july09/linux-next/drivers/clk/clkdev.c:42: undefined reference to `of_clk_get_from_provider'
> make: *** [vmlinux] Error 1
> **/
>
> Any solution?
I'll get a fix out today.
Rob
>
> Thanks & Regards,
> Prashant G
next parent reply other threads:[~2012-07-16 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5003F6DF.2010107@nvidia.com>
2012-07-16 14:19 ` Rob Herring [this message]
2012-07-16 14:19 ` DT clock binding support build break Rob Herring
2012-07-16 11:16 Prashant Gaikwad
2012-07-16 11:28 ` Prashant Gaikwad
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=50042301.6000108@gmail.com \
--to=robherring2@gmail.com \
--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.