Searched refs:destroys (Results 1 – 16 of 16) 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
43 the kernel that destroys the owner task (e.g. due to a SEGFAULT), but
276 Writing '1' to the 'remove' file destroys the mdev device. The vendor driver can
236 destroys an existing rpmsg endpoint. user should provide a pointer
274 closing the device automatically destroys the user.
107 Writing '1' to this file destroys the mediated device. The
125 devm_nvmem_cell_put and devm_nvmem_device_put destroys the devres associated
115 unsigned long destroys; /* number of destroyed neighs */ member
96 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
733 NEIGH_CACHE_STAT_INC(neigh->tbl, destroys); in neigh_destroy()1913 ndst.ndts_destroys += st->destroys; in neightbl_fill_info()2849 st->destroys, in neigh_stat_seq_show()
359 or destroys one.
380 You need to do this because when the bridge driver destroys the i2c adapter
407 destorys||destroys
450 # destroys %d2,%d3,%d4.
243 This destroys the contents of the associative array and leaves it
