On Thu, Feb 03, 2022 at 05:46:55PM +0300, Heikki Krogerus wrote: > +/* These additional details are only available with vSafe5V supplies */ > +static struct kobj_attribute dual_role_power_attr = __ATTR_RO(dual_role_power); > +static struct kobj_attribute usb_suspend_supported_attr = __ATTR_RO(usb_suspend_supported); > +static struct kobj_attribute unconstrained_power_attr = __ATTR_RO(unconstrained_power); > +static struct kobj_attribute usb_communication_capable_attr = __ATTR_RO(usb_communication_capable); > +static struct kobj_attribute dual_role_data_attr = __ATTR_RO(dual_role_data); > +static struct kobj_attribute > +unchunked_extended_messages_supported_attr = __ATTR_RO(unchunked_extended_messages_supported); Note, no 'struct device' should ever have a "raw" kobject hanging off of it. If so, something went wrong. If you do this, userspace will never be notified of the attributes and any userspace representation of the tree will be messed up. Please, use an attribute directory with a name, or if you really need to go another level deep, use a real 'struct device'. As-is here, I can't take it. thanks, greg k-h
