| /openbmc/linux/Documentation/input/ |
| H A D | gameport-programming.rst | 191 pre-filled by cooked data by the caller, max[0..3] should be pre-filled with
|
| /openbmc/linux/Documentation/trace/ |
| H A D | fprobe.rst | 113 somewhere in the caller. This can be used at both entry and exit.
|
| /openbmc/linux/drivers/nvdimm/ |
| H A D | region_devs.c | 1002 const struct device_type *dev_type, const char *caller) in nd_region_create() argument
1016 caller, dev_name(&nvdimm->dev), i, PAGE_SIZE); in nd_region_create()
|
| /openbmc/linux/Documentation/locking/ |
| H A D | ww-mutex-design.rst | 29 to be locked, the caller would be assigned a unique reservation id/ticket,
137 the caller as a signal that an object is twice on the list. This is useful if
|
| /openbmc/linux/drivers/usb/storage/ |
| H A D | uas.c | 79 static int uas_try_complete(struct scsi_cmnd *cmnd, const char *caller);
244 static int uas_try_complete(struct scsi_cmnd *cmnd, const char *caller) in uas_try_complete() argument
|
| /openbmc/linux/mm/ |
| H A D | nommu.c | 155 const void *caller) in __vmalloc_node_range() argument
161 int node, const void *caller) in __vmalloc_node() argument
|
| /openbmc/qemu/docs/user/ |
| H A D | main.rst | 229 environment is a copy of the caller's environment.
|
| /openbmc/openbmc-test-automation/redfish/systems/ |
| H A D | test_led_indicator_asserted.robot | 160 …[Documentation] Verify the LEDs on the power supply units are set according to caller's expectati…
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | devel-algos.rst | 115 the caller should use the functions of crypto_skcipher_alignmask() to
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | v4l2-event.rst | 22 :c:type:`v4l2_kevent` ringbuffer, with the size given by the caller
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | map_devmap.rst | 44 codes up to ``XDP_TX``, as chosen by the caller. The higher bits of ``flags``
|
| /openbmc/linux/drivers/accel/habanalabs/common/ |
| H A D | habanalabs.h | 3609 gfp_t flag, const char *caller);
3611 dma_addr_t dma_handle, const char *caller);
3613 dma_addr_t *dma_handle, const char *caller);
3615 const char *caller);
|
| /openbmc/u-boot/doc/ |
| H A D | README.drivers.eth | 214 and return the result to its caller. The implementation for the write function
|
| H A D | README.virtio | 200 the caller to pass the correct 'struct udevice' id of the virtio device, eg:
|
| /openbmc/linux/Documentation/driver-api/surface_aggregator/clients/ |
| H A D | cdev.rst | 117 the response buffer must be allocated by the caller and passed in via the
|
| /openbmc/qemu/docs/devel/ |
| H A D | multiple-iothreads.txt | 87 loop, depending on which AioContext instance the caller passes in.
|
| H A D | memory.rst | 120 migration to the caller.
131 register the backing memory for migration; the caller must
|
| /openbmc/linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 140 // SAFETY: The safety contract must be upheld by the caller.
|
| /openbmc/linux/fs/btrfs/ |
| H A D | extent-io-tree.c | 57 static inline void __btrfs_debug_check_extent_io_range(const char *caller, in __btrfs_debug_check_extent_io_range() argument
71 caller, btrfs_ino(inode), isize, start, end); in __btrfs_debug_check_extent_io_range()
|
| /openbmc/linux/Documentation/doc-guide/ |
| H A D | kernel-doc.rst | 130 it takes, releases and expects to be held by its caller.
136 * Context: Any context. Expects <lock> to be held by caller.
|
| /openbmc/linux/Documentation/process/ |
| H A D | deprecated.rst | 59 smaller allocation being made than the caller was expecting. Using those
150 If a caller is using non-NUL-terminated strings, strtomem() should be
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | locking.rst | 330 caller, unless ->writepage() returns special WRITEPAGE_ACTIVATE
367 truncated because either the caller holds the folio lock, or the caller
|
| H A D | path-lookup.rst | 294 returned and the caller can know that it lost a race with some other
296 cache, the newly allocated dentry is returned and the caller can
314 has, the dentry is returned and the caller just sees that it lost any
474 component remains for the caller to sort out. Those callers are
481 directory and final component to the caller. The caller will be either
509 example if ``path_parentat()`` reports ``LAST_DOTDOT``, then the caller
1210 otherwise ``-ESTALE`` is returned. When ``-ESTALE`` is returned, the caller may
1301 provided by the caller, so it shouldn't be released when it is no
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | cpu_hotplug.rst | 371 by the setup function and returned to the caller on success.
468 removal, then this number has to be saved by the caller and used
511 If a multi-instance state is removed then the caller has to remove all
|
| /openbmc/linux/Documentation/networking/ |
| H A D | tuntap.rst | 140 created to the caller. Each file descriptor were served as the interface of a
|