Searched full:existing (Results 1 – 25 of 493) sorted by relevance
12345678910>>...20
| /Documentation/block/ |
| D | pr.rst | 64 is non-null. If no existing reservation exists old_key must be zero,
65 if an existing reservation should be replaced old_key must contain
68 If the new_key argument is 0 it unregisters the existing reservation passed
76 devices based on the type argument. The key argument must be the existing
91 This ioctl command releases the existing reservation referred to by
106 registered with the device and drops any existing reservation.
115 Ignore the existing reservation key. This is commonly supported for
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-stm_source | 7 is directed. Reads return an existing connection or "<none>" if
9 Write an existing (registered) stm device's name here to
|
| D | sysfs-bus-intel_th-devices-msc | 19 If operating mode changes, existing buffer is deallocated,
34 Writing to this file deallocates existing buffer (provided
|
| D | evm | 60 existing initialization flags.
90 creating and loading existing trusted/encrypted keys,
|
| /Documentation/driver-api/mei/ |
| D | mei-client-bus.rst | 13 However, for some of the ME functionalities it makes sense to leverage existing software
14 stack and expose them through existing kernel subsystems.
19 Existing device drivers can even potentially be re-used by adding an MEI CL bus layer to
20 the existing code.
26 A driver implementation for an MEI Client is very similar to any other existing bus
|
| /Documentation/devicetree/bindings/net/ |
| D | broadcom-bcm87xx.txt | 12 with the existing register value, and the fourth cell is ORed with
14 value of zero, no read of the existing value is performed.
|
| /Documentation/arch/arm/ |
| D | booting.rst | 30 Existing boot loaders:
46 Existing boot loaders:
66 Existing boot loaders:
80 necessary, but assures that it will not match any existing types.
85 Existing boot loaders:
147 Existing boot loaders:
164 Existing boot loaders:
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom-soc.yaml | 20 When adding new compatibles to existing bindings, use the format in the
21 existing binding, even if it contradicts the above.
37 # Legacy namings - variations of existing patterns/compatibles are OK,
|
| /Documentation/netlink/specs/ |
| D | nftables.yaml | 1198 doc: Delete an existing table.
1208 doc: Delete an existing table with destroy semantics (ignoring ENOENT errors).
1242 doc: Delete an existing chain.
1252 doc: Delete an existing chain with destroy semantics (ignoring ENOENT errors).
1300 doc: Delete an existing rule.
1310 doc: Delete an existing rule with destroy semantics (ignoring ENOENT errors).
1344 doc: Delete an existing set.
1354 doc: Delete an existing set with destroy semantics (ignoring ENOENT errors).
1402 doc: Delete an existing set element.
1412 doc: Delete an existing set element with destroy semantics.
[all …]
|
| /Documentation/timers/ |
| D | hrtimers.rst | 10 features into the existing timer framework, and after testing various
72 special-purpose optimization of the existing timer wheel for the low
88 - simplification of existing, timing related kernel code
105 absolute timers based on a low-resolution CLOCK_REALTIME. The existing
117 existing timer wheel code, as it is mature and well suited. Sharing code
|
| /Documentation/filesystems/ext4/ |
| D | checksums.rst | 13 structures. However, existing 32-bit filesystems cannot be extended to
17 Existing filesystems can have checksumming added by running
|
| /Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 10 For examples of already existing generic drivers that will also be good
28 to any existing kernel subsystem and not be a good fit for an operating system,
|
| /Documentation/networking/device_drivers/fddi/ |
| D | defza.rst | 23 existing IEEE 802.3 10BASE2 Ethernet and IEEE 802.5 Token Ring networks
24 by providing means to reuse existing cabling.
|
| /Documentation/driver-api/usb/ |
| D | dma.rst | 19 manage dma mappings for existing dma-ready buffers (see below).
88 Working with existing buffers
91 Existing buffers aren't usable for DMA without first being mapped into the
|
| /Documentation/networking/device_drivers/atm/ |
| D | cxacru.rst | 15 existing devices working when an invalid configuration is supplied.
17 There is a script cxacru-cf.py to convert an existing file to the sysfs form.
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 15 existing perf buffer, which prompted creation of a new ring buffer
39 with existing perf buffer use in BPF, but would fail if application needed more
56 The approach chosen has an advantage of re-using existing BPF map
59 and utilizing existing tooling (bpftool). For common scenario of using a single
118 Each reserved record is tracked by verifier through existing
|
| D | map_cpumap.rst | 60 helper. This helper replaces existing elements atomically. The ``value`` parameter
74 - BPF_ANY: Create a new element or update an existing element.
76 - BPF_EXIST: Update an existing element.
|
| D | map_sockmap.rst | 132 - ``BPF_ANY``: Create a new element or update an existing element.
134 - ``BPF_EXIST``: Update an existing element.
153 - ``BPF_ANY``: Create a new element or update an existing element.
155 - ``BPF_EXIST``: Update an existing element.
282 - BPF_ANY: Create a new element or update an existing element.
284 - BPF_EXIST: Update an existing element.
315 - BPF_ANY: Create a new element or update an existing element.
317 - BPF_EXIST: Update an existing element.
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvb-frontend-parameters.rst | 15 size would break the existing applications. So, those parameters were
19 existing delivery systems, and to add newer delivery systems.
|
| /Documentation/devicetree/bindings/soc/renesas/ |
| D | renesas-soc.yaml | 21 When adding new compatibles to existing bindings, use the format in the
22 existing binding, even if it contradicts the above.
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 31 erase <keyid> - delete existing user encryption key.
34 master_erase <keyid> - delete existing user encryption key.
71 When doing an update, it is expected that the existing key is removed from
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | clockdomain.txt | 8 binding type, it is used to group existing clock nodes under
|
| /Documentation/userspace-api/media/v4l/ |
| D | fourcc.rst | 11 Existing 4CCs may not obey these guidelines.
|
| /Documentation/dev-tools/kunit/ |
| D | run_manual.rst | 20 - We have an existing kernel configuration to test.
23 - Wish to integrate with some existing testing systems.
|
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 6 additional "shadow" data with existing data structures. Shadow data is
64 * klp_shadow_get_or_alloc() - get existing or alloc a new shadow variable
69 - return existing shadow variable
|
12345678910>>...20