From: Randy Dunlap <rdunlap@xenotime.net>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Vincenzo Frascino <vincenzo.frascino@st.com>
Subject: Re: linux-next: Tree for Feb 29 (spear_thermal.c)
Date: Wed, 29 Feb 2012 18:13:30 -0800 [thread overview]
Message-ID: <4F4EDB4A.4090006@xenotime.net> (raw)
In-Reply-To: <CAP=VYLoDfhM1gh5Ex-kwOECupk5gwHaj1Nx07ByO1u5ujGXYmA@mail.gmail.com>
On 02/29/2012 05:35 PM, Paul Gortmaker wrote:
> On Wed, Feb 29, 2012 at 5:56 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
>> On 02/28/2012 10:52 PM, Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> Changes since 20120228:
>>>
>>> My fixes tree contains:
>>> x86, efi: Fix unaligned access and endian issues--
>>
>>
>> on x86_64:
>>
>> drivers/built-in.o: In function `spear_thermal_exit':
>> spear_thermal.c:(.text+0x49c042): undefined reference to `clk_disable'
>> spear_thermal.c:(.text+0x49c04b): undefined reference to `clk_put'
>> drivers/built-in.o: In function `spear_thermal_probe':
>> spear_thermal.c:(.text+0x49c0e6): undefined reference to `clk_get'
>> spear_thermal.c:(.text+0x49c0fe): undefined reference to `clk_enable'
>> spear_thermal.c:(.text+0x49c196): undefined reference to `clk_put'
>> spear_thermal.c:(.text+0x49c1cc): undefined reference to `clk_disable'
>
> Hi Randy,
>
> I think this should go away once the spear_thermal is limited to
> being built just for that particular ARM platform.
>
> http://www.spinics.net/lists/linux-next/msg18959.html
Yep, thanks.
> Paul.
> --
>
>>
>>
>> Full randconfig file is attached.
>>
>> ---
>> ~Randy
--
~Randy
prev parent reply other threads:[~2012-03-01 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 6:52 linux-next: Tree for Feb 29 Stephen Rothwell
2012-02-29 19:06 ` [PATCH -next] backlight: fix ot200_bl build Randy Dunlap
2012-02-29 22:56 ` linux-next: Tree for Feb 29 (spear_thermal.c) Randy Dunlap
2012-03-01 1:35 ` Paul Gortmaker
2012-03-01 2:13 ` Randy Dunlap [this message]
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=4F4EDB4A.4090006@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sfr@canb.auug.org.au \
--cc=vincenzo.frascino@st.com \
/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