Henrique de Moraes Holschuh пишет: > That just means the ACPI sysfs conversion on that area was not as good as it > should have been. It is hardly the only place where the sysfs ABI is not > well implemented, but that doesn't mean the breakage should remain, or that > it should be made worse. > What is the technical case to returning invalid values for something that is > not supported when you could return a proper error on open() instead (since Power Class interface does not give me control over open() as far as I know. > you're not going to do the Right Thing and not register that attribute it in > the first place)? Not only the "-1" way wastes more system resources (all > clients have to do open+read+close), it also needs userspace to special case > something, and that is always a Bad Idea for *many* reasons. If you know how this could be done, please show the patch... Thanks, Alex. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html