Searched full:responsibility (Results 1 – 25 of 318) sorted by relevance
12345678910>>...13
52 responsibility.62 responsibility.
23 * responsibility for and errors which may appear in this program24 * not any responsibility to update it.
116 We refuse to take any responsibility for that. The driver is provided as-is117 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
94 * It is a responsibility of the master/bridge drivers to add connectors106 * It is a responsibility of the master/bridge drivers to create links278 * It is the responsibility of the entity drivers to add connectors and links.
16 * responsibility of the application to know which sizes are supported on
24 * responsibility of the application to know which sizes are supported on
22 SOFTWARE. Motorola assumes no responsibility for the maintenance
24 * Note that it is the responsibility of the platform driver (or the acpi 5.0
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
62 It's *always* the caller's responsibility to indicate the size of the66 it is providing; it's still the kernel's responsibility to validate
56 * It is the IOMMU driver's responsibility to ensure that the page table
32 * On allocation, both references are the responsibility of the caller. Once the
47 the board support file's responsibility to ensure that the second
21 * It is the responsibility of any person or organization contemplating
268 * The I2C bus driver's responsibility is to pass the in ipmb_slave_cb()272 * address of the responder, it is the responsibility in ipmb_slave_cb()
215 * primary threads to decide who takes up the responsibility.221 * responsibility of TB resync. (Let us call it as thread leader)
48 Maintainers have the right and responsibility to remove, edit, or reject
70 ndo_start_xmit method, it is your driver's responsibility to free
21 Motorola assumes no responsibility for the maintenance and support of the SOFTWARE.
23 * Sends ops to a push buffer, and takes responsibility for unpinning
199 * Note that it is the caller's responsibility to invalidate the TLB after231 * Note that it is the caller's responsibility to invalidate the TLB after