| /linux/net/netlabel/ |
| H A 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
|
| H A 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/drivers/base/ |
| H A D | property.c | 590 * The caller is responsible for calling fwnode_handle_put() on the returned
629 * The caller is responsible for calling fwnode_handle_put() on the returned
704 * The caller is responsible for calling fwnode_handle_put() on the returned
724 * The caller is responsible for calling fwnode_handle_put() on the returned
764 * The caller is responsible for calling fwnode_handle_put() on the returned
792 * The caller is responsible for calling fwnode_handle_put() on the returned
809 * The caller is responsible for calling fwnode_handle_put() on the returned
837 * The caller is responsible for calling fwnode_handle_put() on the returned
865 * The caller is responsible for calling fwnode_handle_put() on the returned
881 * The caller is responsible for calling fwnode_handle_put() on the returned
[all …]
|
| /linux/include/uapi/misc/ |
| H A D | fastrpc.h | 24 * The driver is responsible for cache maintenance when passed
29 * Mapping tagged with a file descriptor. User is responsible for
34 * other than default modes. User is responsible for CPU and DSP
|
| /linux/drivers/acpi/dptf/ |
| H A D | Kconfig | 22 This participant is responsible for exposing platform telemetry:
39 This participant is responsible for exposing:
|
| /linux/Documentation/driver-api/media/ |
| H A 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/security/ |
| H A 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/Documentation/networking/ |
| H A 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
|
| H A 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/sound/soc/intel/avs/ |
| H A D | utils.c | 15 /* Caller responsible for holding adev->modres_mutex. */
31 /* Caller responsible for holding adev->modres_mutex. */
99 /* Caller responsible for holding adev->modres_mutex. */
111 /* Caller responsible for holding adev->modres_mutex. */
|
| /linux/drivers/hwtracing/coresight/ |
| H A D | Kconfig | 27 responsible for transporting and collecting the trace data
67 responsible for bridging the gap between the on-chip coresight
223 SMB is responsible for receiving the trace data from Coresight ETM devices
235 primarily responsible for data set collection and support the
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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/drivers/clk/baikal-t1/ |
| H A D | Kconfig | 8 responsible for the chip subsystems clocking and resetting. It
47 Enable this to support the CCU reset blocks responsible for the
|
| /linux/tools/perf/util/ |
| H A D | llvm-c-helpers.h | 30 * is then responsible for taking that array and convert it into perf's
37 * a newly allocated array with that length. The caller is then responsible
|
| /linux/Documentation/driver-api/ |
| H A 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/Documentation/devicetree/bindings/soc/imx/ |
| H A D | fsl,imx93-src.yaml | 13 The System Reset Controller (SRC) is responsible for the generation of
19 - Responsible for power gating of MIXs (Slices) and their memory
|
| /linux/include/uapi/linux/ |
| H A D | hyperv.h | 202 * is responsible for communicating with the host and responsible for
204 * responsible for data gathering.
229 * is also responsible for binding the key name to the index as well. The
|
| /linux/drivers/slimbus/ |
| H A 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/Documentation/driver-api/soundwire/ |
| H A 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/Documentation/driver-api/acpi/ |
| H A 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/Documentation/driver-api/surface_aggregator/ |
| H A D | overview.rst | 20 Book 2, Surface Laptop 1) and later generation devices, SAM is responsible
29 Laptop 3 and Surface Book 3, is responsible for all major HID input (i.e.
|
| /linux/Documentation/networking/device_drivers/wwan/ |
| H A D | iosm.rst | 51 The userspace application is responsible for all control message fragmentation
74 The userspace management application is responsible for creating new IP link
|
| /linux/drivers/w1/slaves/ |
| H A 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/Documentation/process/ |
| H A D | maintainer-soc.rst | 42 on a vendor level, responsible for multiple product lines. For several reasons,
52 changes. Each architecture has its own maintainers that are responsible for
79 platform-specific maintainers, who are going to be responsible for handling
|
| /linux/Documentation/networking/devlink/ |
| H A D | mlx5.rst | 145 The tx reporter is responsible for reporting and recovering of the following three error scenarios:
176 The rx reporter is responsible for reporting and recovering of the following two error scenarios:
251 It is responsible for querying the vnic diagnostic counters from fw and displaying
|