| 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: Thu, 5 Mar 2009 17:44:18 +0100 From: Jean Delvare <khali@...ux-fr.org> To: djwong@...ibm.com Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel <linux-kernel@...r.kernel.org>, lm-sensors <lm-sensors@...sensors.org> Subject: Re: [PATCH] lm90: Support the MAX6648/6692 chips Hi Darrick, On Thu, 5 Mar 2009 07:47:30 -0800, Darrick J. Wong wrote: > On Thu, Mar 05, 2009 at 03:25:17PM +0100, Jean Delvare wrote: > > I am confused. According to my notes, the MAX6648/MAX6692 is the same > > chip as the MAX6646/MAX6647/MAX6649 (same chip ID of 0x59), the only > > difference being the I2C address (0x4c for the MAX6646, 0x4e for the > > MAX6647 and 0x4d for the MAX6648/MAX6649/MAX6692). So the current code > > should _already_ detect your MAX6648 or MAX6692 as kind = max6646. > > Heh, yep, it does. I guess this patch has been sitting around long > enough to become obsolete, sorry for the unnecessary mail traffic. I > guess we can drop this one. Well, confusion probably would have been avoided if it had been properly documented that the MAX6648 and MAX6692 were already supported. So I think we should still apply the Kconfig part of your patch. Documentation/hwmon/lm90 would need a small update as well. Could you please send an updated patch doing this? I would be happy to apply that. Thanks, -- 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