Searched refs:destroys (Results 1 – 15 of 15) sorted by relevance
112 destroys the devres associated with this PHY.122 Both these APIs destroy the PHY and devm_phy_destroy destroys the devres
39 the kernel that destroys the owner task (e.g. due to a SEGFAULT), but
190 - destroys an existing rpmsg endpoint. user should provide a pointer
261 This destroys the contents of the associative array and leaves it
261 closing the device automatically destroys the user.
1297 This substitution destroys transitivity: in this example, it is perfectly
125 devm_nvmem_cell_put and devm_nvmem_device_put destroys the devres associated
113 unsigned long destroys; /* number of destroyed neighs */ member
92 you would expect. The kernel destroys the old device structure and
95 This destroys the internal HID device. No further I/O will be accepted. There
687 NEIGH_CACHE_STAT_INC(neigh->tbl, destroys); in neigh_destroy()1847 ndst.ndts_destroys += st->destroys; in neightbl_fill_info()2777 st->destroys, in neigh_stat_seq_show()
359 or destroys one.
329 destorys||destroys
450 # destroys %d2,%d3,%d4.
544 You need to do this because when the bridge driver destroys the i2c adapter