Searched refs:releasing (Results 1 – 10 of 10) sorted by relevance
164 * lfree takes an argument to tell the size of the releasing166 releasing point, libc_malloc and libc_free should be used.
150 code that we are releasing through Solaris.303 6176031 the sequence of releasing resource error in e1000gattach690 6870404 e1000g_reset can call e1000g_start after releasing dma resources
1005 pc_lockfs(struct pcfs *fsp, int diskchanged, int releasing) in pc_lockfs() argument1009 if ((fsp->pcfs_flags & PCFS_IRRECOV) && !releasing) in pc_lockfs()
35 # is properly releasing the pages it checks out, and thus avoiding
72 Software without releasing the source code of the75 Apple OS-Developed Software without releasing the
27 The function should sleep for said amount of mili-seconds, releasing the CPU.
408 … responsibility of the upper layer not to acquire too many PTTs without releasing them. Returning …511 …ated cleanup post the ISR release. The function need to be called after releasing all slowpath IRQ…649 The upper layer doesn’t need to take care of allocating/releasing of this interface – it’s part of …
1667 8. Request: Protect releasing LL2/iSCSI/OOO resources flow by NULL checking.2116 Change: Read the error flag before releasing the memory.
6262 useful. When releasing a mutex, the SyncLevel of the mutex must now be