aboutsummaryrefslogtreecommitdiff
path: root/drivers/clocksource/timer-stm32.c
diff options
context:
space:
mode:
authorMatan Barak <[email protected]>2017-08-03 16:07:02 +0300
committerDoug Ledford <[email protected]>2017-08-31 08:35:11 -0400
commit4da70da23e9ba03f7f9e067fbe0eec6ebbfee401 (patch)
tree42e5675db18e41897fed7e6095c8fcbd45917d2a /drivers/clocksource/timer-stm32.c
parent3541030650c0ddb5d52163082fee427b2a453799 (diff)
IB/core: Explicitly destroy an object while keeping uobject
When some objects are destroyed, we need to extract their status at destruction. After object's destruction, this status (e.g. events_reported) relies in the uobject. In order to have the latest and correct status, the underlying object should be destroyed, but we should keep the uobject alive and read this information off the uobject. We introduce a rdma_explicit_destroy function. This function destroys the class type object (for example, the IDR class type which destroys the underlying object as well) and then convert the uobject to be of a null class type. This uobject will then be destroyed as any other uobject once uverbs_finalize_object[s] is called. Signed-off-by: Matan Barak <[email protected]> Reviewed-by: Yishai Hadas <[email protected]> Signed-off-by: Doug Ledford <[email protected]>
Diffstat (limited to 'drivers/clocksource/timer-stm32.c')
0 files changed, 0 insertions, 0 deletions