I am aware that it it is always recommended that attributes must be associate via attribute groups when calling device_register() . This way when the device is created, user space can always see attributes once they get device create notification via uevent.
I have need to create/delete attributes on fly using device_create_file/device_remove_file. In past several drivers did that.
But with the enforcements of device model for new class of drivers, is it a big NO? I am not aware of change notification calls other than for kobject_uevent.
Thanks, Srinivas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
