| 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
| ||
|
Date: Fri, 20 Nov 2009 12:30:16 +0100 From: Jean Delvare <khali@...ux-fr.org> To: Clemens Ladisch <clemens@...isch.de> Cc: Serge Belyshev <belyshev@...ni.sinp.msu.ru>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, lm-sensors@...sensors.org Subject: Re: [lm-sensors] [PATCH v2] k10temp: temperature sensor for AMD Family 10h/11h CPUs On Fri, 20 Nov 2009 11:47:51 +0100, Clemens Ladisch wrote: > This adds a driver for the internal temperature sensor of AMD Family 10h > and 11h CPUs. > > Signed-off-by: Clemens Ladisch <clemens@...isch.de> > --- > v2: Erratum 319 now results in a warning, not an error, because it cannot > be reliably detected; Serge Belyshev reports that his CPU sensor works. Nack. Unreliable sensors -> the default must be to NOT bind to these CPUs. Feel free to provide a way to force the bind to happen (and still print a big fat warning that this is a very bad idea), but do NOT make it the default. Otherwise your driver will _never_ make it into the kernel tree. As a side note I'd be curious to see what Serge calls "working sensors". We had several reports in the past of people who claimed that their sensors were working. After looking at their numbers, I had doubt this really was the case. -- 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/
Powered by blists - more mailing lists