Searched refs:destroys (Results 1 – 22 of 22) sorted by relevance
146 destroys the devres associated with this PHY.157 Both these APIs destroy the PHY and devm_phy_destroy destroys the devres
38 * destroys the event list
45 - destroys the event list
108 Writing '1' to this file destroys the mediated device. The
125 scalability, destroys real-time response, degrades battery
37 The _trace_seq_destroy()_ function destroys the trace sequence _s_ and frees
163 devm_nvmem_cell_put and devm_nvmem_device_put destroys the devres associated
262 Writing '1' to the 'remove' file destroys the mdev device. The vendor driver can
274 closing the device automatically destroys the user.
114 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
43 the kernel that destroys the owner task (e.g. due to a SEGFAULT), but
119 and then destroys the watch_list object itself.
416 or destroys one.
236 destroys an existing rpmsg endpoint. user should provide a pointer
834 NEIGH_CACHE_STAT_INC(neigh->tbl, destroys); in neigh_destroy()2090 ndst.ndts_destroys += st->destroys; in neightbl_fill_info()3330 st->destroys, in neigh_stat_seq_show()
450 # destroys %d2,%d3,%d4.
243 This destroys the contents of the associative array and leaves it
469 destorys||destroys
472 You need to do this because when the bridge driver destroys the i2c adapter
