From: Jean Delvare <khali@linux-fr.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
lm-sensors@lm-sensors.org, linux-next@vger.kernel.org,
Huaxu Wan <huaxu.wan@intel.com>
Subject: Re: [lm-sensors] linux-next: Tree for June 29 (hwmon/coretemp)
Date: Tue, 29 Jun 2010 21:38:37 +0200 [thread overview]
Message-ID: <20100629213837.50a64edc@hyperion.delvare> (raw)
In-Reply-To: <20100629210532.314250ba@hyperion.delvare>
On Tue, 29 Jun 2010 21:05:32 +0200, Jean Delvare wrote:
> Hi Randy,
>
> On Tue, 29 Jun 2010 08:02:57 -0700, Randy Dunlap wrote:
> > On Tue, 29 Jun 2010 15:19:38 +1000 Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > Changes since 20100628:
> > >
> > > My fixes tree is now empty.
> >
> >
> > when CONFIG_SMP is not enabled:
> >
> > drivers/hwmon/coretemp.c:308: error: 'struct cpuinfo_x86' has no member named 'cpu_core_id'
> > drivers/hwmon/coretemp.c:428: error: 'struct cpuinfo_x86' has no member named 'phys_proc_id'
> > drivers/hwmon/coretemp.c:429: error: 'struct cpuinfo_x86' has no member named 'cpu_core_id'
> > drivers/hwmon/coretemp.c:457: error: 'struct cpuinfo_x86' has no member named 'phys_proc_id'
> > drivers/hwmon/coretemp.c:458: error: 'struct cpuinfo_x86' has no member named 'cpu_core_id'
>
> Thanks for the heads up, I hadn't considered the no-SMP case. I'll take
> a look immediately.
Should be fixed now, thanks again.
--
Jean Delvare
next prev parent reply other threads:[~2010-06-29 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 5:19 linux-next: Tree for June 29 Stephen Rothwell
2010-06-29 15:02 ` linux-next: Tree for June 29 (hwmon/coretemp) Randy Dunlap
2010-06-29 19:05 ` [lm-sensors] " Jean Delvare
2010-06-29 19:38 ` Jean Delvare [this message]
2010-06-29 15:07 ` linux-next: Tree for June 29 (staging/spectra) 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=20100629213837.50a64edc@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=huaxu.wan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=randy.dunlap@oracle.com \
--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