Searched refs:destroys (Results 1 – 21 of 21) sorted by relevance
173 destroys the devres associated with this PHY.184 Both these APIs destroy the PHY and devm_phy_destroy destroys the devres
108 Writing '1' to this file destroys the mediated device. The
38 * destroys the event list
45 - destroys the event list
139 scalability, destroys real-time response, degrades battery
159 devm_nvmem_cell_put and devm_nvmem_device_put destroys the devres associated
235 Writing '1' to the 'remove' file destroys the mdev device. The vendor driver can
291 closing the device automatically destroys the user.
117 unsigned long destroys; /* number of destroyed neighs */ member
39 decreased it destroys the extra worker threads. So, after connection is
96 you would expect. The kernel destroys the old device structure and
96 This destroys the internal HID device. No further I/O will be accepted. There
119 and then destroys the watch_list object itself.
243 This destroys the contents of the associative array and leaves it
43 the kernel that destroys the owner task (e.g. due to a SEGFAULT), but
414 or destroys one.
236 destroys an existing rpmsg endpoint. user should provide a pointer
886 NEIGH_CACHE_STAT_INC(neigh->tbl, destroys); in neigh_destroy()2213 ndst.ndts_destroys += READ_ONCE(st->destroys); in neightbl_fill_info()3472 st->destroys, in neigh_stat_seq_show()
450 # destroys %d2,%d3,%d4.
494 destorys||destroys
508 You need to do this because when the bridge driver destroys the i2c adapter
