linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for October 1 (hwmon/pkgtemp)
Date: Mon, 11 Oct 2010 10:05:01 -0700	[thread overview]
Message-ID: <4CB343BD.9030605@oracle.com> (raw)
In-Reply-To: <20101004184445.GA31377@linux-os.sc.intel.com>

On 10/04/10 11:44, Fenghua Yu wrote:
> On Fri, Oct 01, 2010 at 03:43:14PM -0700, Randy Dunlap wrote:
>> On Fri, 1 Oct 2010 15:37:56 +1000 Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> Changes since 20100930:
>>
>>
>> drivers/hwmon/pkgtemp.c:356: error: implicit declaration of function 'cpu_core_mask'
>>
>> CONFIG_SMP is not set.
>>
>> config is attached.
>>
> 
> From: Fenghua Yu <fenghua.yu@intel.com>
> Date: Mon, 4 Oct 2010 11:00:36 -0700
> Subject: [PATCH] hwmon (pkgtemp): Fix build failure for UP
> 
> This fix is only a workaround. Another fix is to add #ifdef CONFIG_SMP around
> cpu_core_mask. But the code will not be cleaner than this fix.  This fix is
> similar to coretemp in commit fff2017354a3a9906862aabbf2a1cae5b4330e40.
> 
> For a real fix, cpu_core_mask() should be defined in UP include code, eg in
> linux/smp.h, and asm/smp.h should not be included directly. This fix is
> currently not possible because asm/smp.h define cpu_core_mask() unconditionally
> and is included directly from many source files.
> 
> In the long run, both cpu_sibling_mask and cpu_core_mask will be defined in UP
> and this workaround and the workaround in coretemp can be removed.
> 
> Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Guenter Roeck <guenter.roeck@ericsson.com>

Acked-by: Randy Dunlap <randy.dunlap@oracle.com>

Thanks.

> ---
>  drivers/hwmon/pkgtemp.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/hwmon/pkgtemp.c b/drivers/hwmon/pkgtemp.c
> index c9f652d..36d96c7 100644
> --- a/drivers/hwmon/pkgtemp.c
> +++ b/drivers/hwmon/pkgtemp.c
> @@ -32,6 +32,7 @@
>  #include <linux/list.h>
>  #include <linux/platform_device.h>
>  #include <linux/cpu.h>
> +#include <asm/smp.h>
>  #include <asm/msr.h>
>  #include <asm/processor.h>
>  


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-10-11 17:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  5:37 linux-next: Tree for October 1 Stephen Rothwell
2010-10-01 22:41 ` linux-next: Tree for October 1 (staging/ft1000) Randy Dunlap
2010-10-04  8:29   ` Arnd Bergmann
2010-10-01 22:43 ` linux-next: Tree for October 1 (hwmon/pkgtemp) Randy Dunlap
2010-10-04 18:44   ` Fenghua Yu
2010-10-11 17:05     ` Randy Dunlap [this message]
2010-10-01 22:45 ` linux-next: Tree for October 1 (staging/olpc_dcon) Randy Dunlap
2010-10-02  2:24   ` Andres Salomon
2010-10-02 18:51     ` Greg KH
2010-10-03  1:03       ` Andres Salomon
2010-10-05 19:08         ` Greg KH
2010-10-05 19:33           ` Andres Salomon

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=4CB343BD.9030605@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).