Searched full:responsibility (Results 1 – 25 of 314) sorted by relevance
12345678910>>...13
16 /* It is the caller's responsibility to free the pointer returned here */35 /* It is the caller's responsibility to free the pointer returned here */81 /* It is the caller's responsibility to free the pointer returned here */147 /* It is the caller's responsibility to free the pointer returned here */
23 * responsibility for and errors which may appear in this program24 * not any responsibility to update it.
113 We refuse to take any responsibility for that. The driver is provided as-is114 and YOU USE IT AT YOUR OWN RESPONSIBILITY.
103 * The driver's only responsibility is to fill in the type and the data118 * The driver's only responsibility is to fill in the type and the data
91 * It is a responsibility of the master/bridge drivers to add connectors103 * It is a responsibility of the master/bridge drivers to create links277 * It is the responsibility of the entity drivers to add connectors and links.
20 * responsibility of the application to know which sizes are supported on
26 * responsibility of the application to know which sizes are supported on
121 c. Affirmer disclaims responsibility for clearing rights of other persons124 Further, Affirmer disclaims responsibility for obtaining any necessary
22 SOFTWARE. Motorola assumes no responsibility for the maintenance
36 In this mode, when a cache miss occurs, responsibility for fetching
35 * function's responsibility to free message if dynamically allocated.
43 responsibility.
123 parallel() will take responsibility for the job from this point. The job153 It is the user's responsibility to ensure all outstanding jobs are complete
145 responsibility to save IO target specific info in userspace.214 responsibility to recover the device context by its own knowledge.342 be trusted, because it is ublk server's responsibility to make sure IO buffer
16 * is non-reentrant. It is the caller's responsibility to avoid reentrance.
87 * It is the IOMMU driver's responsibility to ensure that the page table
31 interface. Said functionality is the responsibility of the respective
12 own FDTs. Interpreting those sub FDTs is the responsibility of KHO users.
30 * It is the driver's responsibility to update sw_state and hw_state.
48 Maintainers have the right and responsibility to remove, edit, or reject
16 their responsibility (their domain) can be accesssed by which compartment. A
32 * On allocation, both references are the responsibility of the caller. Once the