Home
last modified time | relevance | path

Searched full:responsibility (Results 1 – 25 of 363) sorted by relevance

12345678910>>...15

/Linux-v6.1/arch/powerpc/platforms/83xx/
DKconfig52 responsibility.
62 responsibility.
/Linux-v6.1/arch/microblaze/lib/
Dmemset.c23 * responsibility for and errors which may appear in this program
24 * not any responsibility to update it.
Dmemcpy.c23 * responsibility for and errors which may appear in this program
24 * not any responsibility to update it.
Dmemmove.c23 * responsibility for and errors which may appear in this program
24 * not any responsibility to update it.
/Linux-v6.1/Documentation/gpu/amdgpu/display/
Ddcn-overview.rst60 OPP. It is DC's responsibility to drive the best configuration for each
101 to choose which link encoder to connect to which PHY. FE's main responsibility
183 configuration, and it is the DML's responsibility to set up all required
/Linux-v6.1/include/media/
Dv4l2-event.h103 * The driver's only responsibility is to fill in the type and the data
118 * The driver's only responsibility is to fill in the type and the data
/Linux-v6.1/Documentation/scsi/
Ddc395x.rst116 We refuse to take any responsibility for that. The driver is provided as-is
117 and YOU USE IT AT YOUR OWN RESPONSIBILITY.
/Linux-v6.1/include/uapi/linux/
Dmedia.h91 * It is a responsibility of the master/bridge drivers to add connectors
103 * It is a responsibility of the master/bridge drivers to create links
277 * It is the responsibility of the entity drivers to add connectors and links.
Dmemfd.h16 * responsibility of the application to know which sizes are supported on
Dmman.h24 * responsibility of the application to know which sizes are supported on
/Linux-v6.1/fs/cachefiles/
DKconfig36 In this mode, when a cache miss occurs, responsibility for fetching
/Linux-v6.1/arch/m68k/fpsp040/
DREADME22 SOFTWARE. Motorola assumes no responsibility for the maintenance
/Linux-v6.1/tools/include/uapi/linux/
Dmman.h24 * responsibility of the application to know which sizes are supported on
/Linux-v6.1/Documentation/core-api/
Dpadata.rst123 parallel() will take responsibility for the job from this point. The job
153 It is the user's responsibility to ensure all outstanding jobs are complete
/Linux-v6.1/Documentation/userspace-api/
Diommu.rst62 It's *always* the caller's responsibility to indicate the size of the
66 it is providing; it's still the kernel's responsibility to validate
/Linux-v6.1/drivers/iommu/
Dio-pgtable.c64 * It is the IOMMU driver's responsibility to ensure that the page table
/Linux-v6.1/kernel/
Dcontext_tracking.c553 * responsibility to call into context tracking with IRQs disabled.
586 * responsibility to call into context tracking with IRQs disabled.
661 * responsibility to call into context tracking with IRQs disabled.
685 * user_exit_irqoff(). It should be the arch entry code responsibility to
/Linux-v6.1/Documentation/leds/
Dwell-known-leds.txt28 Note: tracking and management of Player IDs is the responsibility of user space,
/Linux-v6.1/include/linux/sunrpc/
Dgss_asn1.h21 * It is the responsibility of any person or organization contemplating
/Linux-v6.1/fs/xfs/
Dxfs_extfree_item.h32 * On allocation, both references are the responsibility of the caller. Once the
/Linux-v6.1/Documentation/arm/samsung-s3c24xx/
Dusb-host.rst47 the board support file's responsibility to ensure that the second
/Linux-v6.1/drivers/platform/surface/aggregator/
DKconfig31 interface. Said functionality is the responsibility of the respective
/Linux-v6.1/drivers/char/ipmi/
Dipmb_dev_int.c268 * 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()
/Linux-v6.1/include/drm/
Ddrm_privacy_screen_driver.h30 * It is the driver's responsibility to update sw_state and hw_state.
/Linux-v6.1/Documentation/networking/
Ddriver.rst70 ndo_start_xmit method, it is your driver's responsibility to free

12345678910>>...15