linux-kernel - Re: [lm-sensors] linux-next: Tree for June 29 (hwmon/coretemp)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100629213837.50a64edc@hyperion.delvare>
Date:	Tue, 29 Jun 2010 21:38:37 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	LKML <linux-kernel@...r.kernel.org>, lm-sensors@...sensors.org,
	linux-next@...r.kernel.org, Huaxu Wan <huaxu.wan@...el.com>
Subject: Re: [lm-sensors] linux-next: Tree for June 29 (hwmon/coretemp)

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
--
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/