linux-kernel - Re: linux-next: Tree for Feb 29 (spear

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Feb 2012 20:35:06 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Vincenzo Frascino <vincenzo.frascino@...com>
Subject: Re: linux-next: Tree for Feb 29 (spear_thermal.c)

On Wed, Feb 29, 2012 at 5:56 PM, Randy Dunlap <rdunlap@...otime.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

Paul.
--

>
>
> Full randconfig file is attached.
>
> ---
> ~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/