Searched full:responsible (Results 1 – 25 of 985) sorted by relevance
12345678910>>...40
| /linux-5.10/net/netlabel/ |
| D | netlabel_addrlist.c | 43 * responsible for calling the rcu_read_[un]lock() functions.
66 * it is returned, otherwise NULL is returned. The caller is responsible for
93 * responsible for calling the rcu_read_[un]lock() functions.
117 * it is returned, otherwise NULL is returned. The caller is responsible for
144 * returned, otherwise a negative value is returned. The caller is responsible
181 * returned, otherwise a negative value is returned. The caller is responsible
217 * Remove the specified IP address entry. The caller is responsible for
235 * entry on success, NULL on failure. The caller is responsible for calling
257 * Remove the specified IP address entry. The caller is responsible for
275 * entry on success, NULL on failure. The caller is responsible for calling
|
| D | netlabel_domainhash.c | 100 * correct bucket number for the domain. The caller is responsible for
132 * which matches any address family entries. The caller is responsible for
168 * entries. The caller is responsible ensuring that the hash table is
204 * the given information. Caller is responsible for holding the necessary
576 * lower level protocol handler (i.e. CIPSO). Caller is responsible for
853 * NULL. The caller is responsible for ensuring that rcu_read_[un]lock() is
872 * responsible for ensuring that rcu_read_[un]lock() is called.
902 * responsible for ensuring that rcu_read_[un]lock() is called.
|
| /linux-5.10/drivers/acpi/dptf/ |
| D | Kconfig | 25 This participant is responsible for exposing platform telemetry:
42 This participant is responsible for exposing:
|
| /linux-5.10/Documentation/driver-api/media/ |
| D | dtv-core.rst | 8 - A bridge driver that is responsible to talk with the bus where the other
15 the hardware responsible for tuning into a digital TV transponder or
|
| /linux-5.10/Documentation/networking/ |
| D | nfc.rst | 14 The NFC subsystem is responsible for:
19 The subsystem is divided in some parts. The 'core' is responsible for
21 responsible for providing an interface to control operations and low-level
|
| D | cdc_mbim.rst | 97 responsible for negotiating a control message size complying with the
110 The userspace application is responsible for all control message
183 The userspace management application is responsible for adding new
224 The DSS supporting userspace management application is responsible for
|
| /linux-5.10/security/ |
| D | inode.c | 101 * is unloaded, you are responsible here). If an error occurs, the
194 * you are responsible here). If an error occurs, the function will return
222 * you are responsible here). If an error occurs, the function will return
254 * you are responsible here). If an error occurs, the function will return
293 * removed; you are responsible here.
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-stateless-decoder.rst | 11 of any previous and future frames, and that the client is responsible for
21 cost of this simplicity is extra complexity in the client which is responsible
56 The client is responsible for making sure that these controls are set
200 is responsible for deducing the minimum number of buffers required
231 For each frame, the client is responsible for submitting at least one request to
375 for H.264) may have changed and the client is responsible for making sure that a
|
| /linux-5.10/Documentation/driver-api/ |
| D | slimbus.rst | 31 A manager device is responsible for enumeration, configuration, and dynamic
36 Framer device is responsible for clocking the bus, and transmitting frame-sync
49 responsible to select the active-framer for clocking the bus.
|
| /linux-5.10/include/uapi/linux/ |
| D | hyperv.h | 191 * is responsible for communicating with the host and responsible for
193 * responsible for data gathering.
218 * is also responsible for binding the key name to the index as well. The
|
| /linux-5.10/Documentation/admin-guide/media/ |
| D | davinci-vpbe.rst | 27 When connected to an external encoder, vpbe controller is also responsible
38 Responsible for setting outputs provided through internal DACs and also
|
| /linux-5.10/Documentation/powerpc/ |
| D | cxlflash.rst | 32 responsible for the initialization of the adapter, setting up the
205 This ioctl is responsible for transitioning the LUN to direct
222 This ioctl is responsible for transitioning the LUN to virtual mode
253 This ioctl is responsible for resizing a previously created virtual
272 This ioctl is responsible for releasing a previously obtained
285 This ioctl is responsible for unregistering a context with the
297 This ioctl is responsible for cloning a previously created
|
| /linux-5.10/Documentation/networking/devlink/ |
| D | devlink-info.rst | 158 Control unit firmware version. This firmware is responsible for house
181 Version of the software responsible for supporting/handling the
193 RoCE firmware version which is responsible for handling roce
|
| /linux-5.10/drivers/staging/unisys/Documentation/ABI/ |
| D | sysfs-platform-visorchipset | 59 responsible for enabling and disabling SR-IOV devices when the
78 responsible for enabling and disabling SR-IOV devices when the
|
| /linux-5.10/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 27 not be responsible for the errors so resetting them individually is not a
64 or Master driver implementers are responsible for writing valid values in
|
| /linux-5.10/drivers/slimbus/ |
| D | slimbus.h | 93 * responsible for clocking the bus.
94 * Manager is responsible for framer hand-over.
380 * 'Manager device' is responsible for device management, bandwidth
389 * Manager is also responsible for entering (and exiting) low-power-mode
396 * device'. Interface device is responsible for monitoring the bus and
|
| /linux-5.10/tools/perf/Documentation/ |
| D | perf-c2c.txt | 220 - pid of the process responsible for the accesses
223 - tid of the process responsible for the accesses
226 - code address responsible for the accesses
|
| /linux-5.10/Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 59 that means that the handler has claimed the device node and is now responsible
61 be responsible for preparing the device node for unregistration in that case.
|
| /linux-5.10/drivers/w1/slaves/ |
| D | Kconfig | 126 as the one who is responsible for charging/discharging/monitoring
138 as the one who is responsible for charging/discharging/monitoring
|
| /linux-5.10/drivers/soc/sunxi/ |
| D | Kconfig | 11 device is responsible on mapping the SRAM in the sunXi SoCs
|
| /linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | mt6323-poweroff.txt | 3 The power controller which could be found on PMIC is responsible for externally
|
| /linux-5.10/drivers/hwtracing/coresight/ |
| D | Kconfig | 26 responsible for transporting and collecting the trace data
66 responsible for bridging the gap between the on-chip coresight
|
| /linux-5.10/drivers/mtd/maps/ |
| D | sc520cdp.c | 37 ** responsible PARxx registers in the SC520's MMCR region. This will
186 ** Find the PARxx registers that are responsible for activating in sc520cdp_setup_par()
202 printk(KERN_NOTICE "Could not find PAR responsible for %s\n", in sc520cdp_setup_par()
|
| /linux-5.10/arch/powerpc/kvm/ |
| D | book3s_hv_ras.c | 208 * subcore status. Only primary threads from each subcore is responsible
266 * If resync_req == true, then this thread is responsible to in kvmppc_realmode_hmi_handler()
293 * Check if this thread is responsible to resync TB. in kvmppc_realmode_hmi_handler()
|
| /linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | sirf-audio-port.txt | 10 One of the DMA channels will be responsible for transmission (should be
|
12345678910>>...40