Displaying 3 results from an estimated 3 matches for "dev_release".
Did you mean:
adev_release
2020 Feb 13
0
[PATCH V2 3/5] vDPA: introduce vDPA bus
...doesn't call the bus release?
What it did is:
??????? if (dev->release)
??????????????? dev->release(dev);
??????? else if (dev->type && dev->type->release)
??????????????? dev->type->release(dev);
??????? else if (dev->class && dev->class->dev_release)
??????????????? dev->class->dev_release(dev);
??????? else
??????????????? WARN(1, KERN_ERR "Device '%s' does not have a release()
function, it is broken and must be fixed. See Documentation/kobject.txt.\n",
??????????????????????? dev_name(dev));
So it looks not.
&...
2020 Feb 12
2
[PATCH V2 3/5] vDPA: introduce vDPA bus
On Wed, Feb 12, 2020 at 03:55:31PM +0800, Jason Wang wrote:
> > The ida_simple_remove should probably be part of the class release
> > function to make everything work right
>
> It looks to me bus instead of class is the correct abstraction here since
> the devices share a set of programming interface but not the semantics.
device_release() doesn't call the bus release?
2020 Feb 12
2
[PATCH V2 3/5] vDPA: introduce vDPA bus
On Wed, Feb 12, 2020 at 03:55:31PM +0800, Jason Wang wrote:
> > The ida_simple_remove should probably be part of the class release
> > function to make everything work right
>
> It looks to me bus instead of class is the correct abstraction here since
> the devices share a set of programming interface but not the semantics.
device_release() doesn't call the bus release?