On Sat, Dec 18, 2010 at 04:30:12PM +0100, Henrik Rydberg wrote: > > Hm. Is this an oops or a lockdep warning? > > It is a null-pointer dereference in sysfs_create_file(). Probably the > kernel is asking the same question as I did - do you actually see the > sysfs nodes when testing the patch? Yup. Not sure what's happening there. I'll try to figure that out. > > > So where to attach the sysfs nodes... There is also a userspace issue > > > here, since a lot of applications are hard-wired to > > > /sys/devices/platform/applesmc.768/. > > > > The correct sysfs ABI is to use the /sys/class interface and the names > > under there rather than assuming a hardwired platform device path. > > Still breaks user-space, but it seems this is already under control. If it turns out that there's code that relies on it then we could obviously retain the platform device, but it's kind of ugly. sysfs paths aren't intended to be hardcoded. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
