Searched full:responsibility (Results 1 – 25 of 78) sorted by relevance
1234
113 We refuse to take any responsibility for that. The driver is provided as-is114 and YOU USE IT AT YOUR OWN RESPONSIBILITY.
60 OPP. It is DC's responsibility to drive the best configuration for each101 to choose which link encoder to connect to which PHY. FE's main responsibility183 configuration, and it is the DML's responsibility to set up all required
48 Maintainers have the right and responsibility to remove, edit, or reject
76 a kernel manager have huge fiscal responsibility **anyway**, it's usually278 Since your main responsibility seems to be to take the blame for other
44 responsibility is upon all of us, and ultimately the Code of Conduct
16 their responsibility (their domain) can be accesssed by which compartment. A
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
148 It is the driver's responsibility to make sure that the machine isn't
103 It is the VMM responsibility to describe this to the guest, the pvIOMMU
40 It is the responsibility of the low level hardware driver to perform the
42 assigned to the requesting hosts. It is the drivers responsibility to keep
40 It is the responsibility of the interrupt controller's binding to define the
72 PERSONS AND ORGANIZATIONS WHO CAN AND WILL TAKE FULL RESPONSIBILITY FOR ANY
75 is the caller's responsibility.
28 Note: tracking and management of Player IDs is the responsibility of user space,
116 ndo_start_xmit method, it is your driver's responsibility to free
9 that device. It is the responsibility of the device driver and/or the
14 I DISCLAIM ALL RESPONSIBILITY FOR ANY POSSIBLE BAD EFFECTS OF THIS CODE!
136 Note also that it is your responsibility to not create hard link
145 responsibility to save IO target specific info in userspace.208 responsibility to recover the device context by its own knowledge.
202 It is the responsibility of userspace to negotiate an acceptable format+modifier321 whatever heuristic. It is the implementation's responsibility to ensure that
159 - It's the driver's responsibility to ensure that the RX and TX completion
165 * It is UMDs responsibility to ensure the mapping is no longer in use before
87 The driver's only responsibility is to fill in the type and the data fields.
176 the responsibility of user space to detect card crashes via