All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 17 (x86_pkg_temp_thermal.c)
Date: Mon, 17 Jun 2013 10:26:27 -0700	[thread overview]
Message-ID: <51BF46C3.3090900@linux.intel.com> (raw)
In-Reply-To: <51BF4159.1000004@infradead.org>

On 06/17/2013 10:03 AM, Randy Dunlap wrote:
> On 06/17/13 01:51, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130607:
>>
>
> on i386 and x86_64:
>
> when built as loadable module:
>
> ERROR: "platform_thermal_package_rate_control" [drivers/thermal/x86_pkg_temp_thermal.ko] undefined!
> ERROR: "platform_thermal_package_notify" [drivers/thermal/x86_pkg_temp_thermal.ko] undefined!
>
> or when built-in:
>
> drivers/built-in.o: In function `pkg_temp_thermal_init':
> x86_pkg_temp_thermal.c:(.init.text+0x1492b): undefined reference to `platform_thermal_package_notify'
> x86_pkg_temp_thermal.c:(.init.text+0x14936): undefined reference to `platform_thermal_package_rate_control'
> x86_pkg_temp_thermal.c:(.init.text+0x150fe): undefined reference to `platform_thermal_package_notify'
> x86_pkg_temp_thermal.c:(.init.text+0x15109): undefined reference to `platform_thermal_package_rate_control'
> drivers/built-in.o: In function `pkg_temp_thermal_exit':
> x86_pkg_temp_thermal.c:(.exit.text+0x3a9b): undefined reference to `platform_thermal_package_notify'
> x86_pkg_temp_thermal.c:(.exit.text+0x3aa6): undefined reference to `platform_thermal_package_rate_control'
>
>
> Full randconfig file is attached (for loadable module build).
>
>
>

This requires CONFIG_X86_MCE, which is by default is set to "y".

Thanks,
Srinivas


  reply	other threads:[~2013-06-17 17:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  8:51 linux-next: Tree for Jun 17 Stephen Rothwell
2013-06-17  8:51 ` Stephen Rothwell
2013-06-17 10:04 ` Geert Uytterhoeven
2013-06-18  0:06   ` Stephen Rothwell
2013-06-17 17:03 ` linux-next: Tree for Jun 17 (x86_pkg_temp_thermal.c) Randy Dunlap
2013-06-17 17:26   ` Srinivas Pandruvada [this message]
2013-06-17 17:55     ` [PATCH -next] thermal: fix x86_pkg_temp_thermal.c build and Kconfig Randy Dunlap
2013-06-17 18:09       ` Srinivas Pandruvada
2013-06-17 18:12         ` [PATCH -next v2] " Randy Dunlap
2013-06-17 18:17           ` Borislav Petkov
2013-06-17 18:31             ` Srinivas Pandruvada
2013-06-17 19:27             ` [PATCH -next v3] " Randy Dunlap
2013-06-17 19:45               ` Borislav Petkov
2013-06-17 23:28                 ` Zhang Rui
2013-06-17 17:15 ` linux-next: Tree for Jun 17 (compat_binfmt_elf.c) Randy Dunlap
2013-06-18  0:24   ` Stephen Rothwell
2013-06-18 19:33     ` [PATCH -next] x86: fix build error and kconfig for ia32_emulation and binfmt Randy Dunlap
2013-06-19  0:18       ` [tip:x86/urgent] " tip-bot for Randy Dunlap
2013-06-17 17:26 ` linux-next: Tree for Jun 17 (media/usb/uvc) Randy Dunlap

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=51BF46C3.3090900@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.