Searched full:propagated (Results 1 – 25 of 137) sorted by relevance
123456
| /linux-5.10/Documentation/networking/ |
| D | mpls-sysctl.rst | 31 Control whether TTL is propagated from the IPv4/IPv6 header to
32 the MPLS header on imposing labels and propagated from the
43 propagated from an IP header, either because one isn't present
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | v4l2-selection-flags.rst | 40 - The configuration must not be propagated to any further processing
41 steps. If this flag is not given, the configuration is propagated
|
| D | dev-subdev.rst | 189 - Formats should be propagated from sink pads to source pads. Modifying
198 Formats are not propagated across links, as that would involve
411 made will be propagated to any subsequent stages. If this behaviour is
|
| /linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 91 Notice that new whitelist entries will not be propagated::
130 to devices will be propagated down the hierarchy.
131 For every propagated exception, the effective rules will be re-evaluated based
|
| /linux-5.10/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 33 become active. The active channel is propagated to other CTIs via the CTM,
51 (e.g. UART), or be propagated off chip as hardware IO lines.
166 * ``chan_set``: Set the channel - the set state will be propagated around
|
| /linux-5.10/Documentation/devicetree/bindings/media/i2c/ |
| D | imi,rdacm2x-gmsl.yaml | 53 propagated on the local I2C bus to the remote device there connected. All the
55 propagated to the remote de-serializer encapsulated in the GMSL control
|
| /linux-5.10/drivers/staging/media/imx/ |
| D | TODO | 8 (which should be propagated if necessary) to get this info. However
|
| /linux-5.10/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 45 and all propagated stores from other CPUs must propagate to all
52 stores on the same CPU and all propagated stores from other CPUs
|
| /linux-5.10/include/uapi/linux/ |
| D | batadv_packet.h | 131 * @BATADV_TT_OGM_DIFF: TT diff propagated through OGM
558 * struct batadv_tvlv_gateway_data - gateway data propagated through gw tvlv
569 * struct batadv_tvlv_tt_data - tt data propagated through the tt tvlv container
582 * struct batadv_tvlv_tt_vlan_data - vlan specific tt data propagated through
|
| /linux-5.10/arch/x86/kvm/mmu/ |
| D | spte.h | 62 * Bits 0-8 of the MMIO generation are propagated to spte bits 3-11
63 * Bits 9-17 of the MMIO generation are propagated to spte bits 54-62
|
| /linux-5.10/Documentation/devicetree/bindings/clock/ti/ |
| D | fixed-factor-clock.txt | 23 - ti,set-rate-parent: clk_set_rate is propagated to parent
|
| D | mux.txt | 49 - ti,set-rate-parent : clk_set_rate is propagated to parent clock,
|
| D | divider.txt | 77 - ti,set-rate-parent : clk_set_rate is propagated to parent
|
| /linux-5.10/tools/memory-model/Documentation/ |
| D | explanation.txt | 743 other store to the same location which has already propagated to CPU C.
753 propagated to that CPU.
1106 first load, the value x = 1 must have propagated to P1 before the
1168 that W's store must have propagated to R's CPU before R executed;
1222 order, and P1's store propagated to P0 before P0's load executed.
1244 then the x = 9 store must have been propagated to P0 before the first
1248 P1's store propagated to P0 before P0's second load executed.
1283 have propagated to P1 by the time P1's load from buf executed, so r2
1338 store to z has propagated to P0 (an rfe link).
1382 have propagated to E's CPU before E executed. If E was a store, the
[all …]
|
| /linux-5.10/Documentation/translations/ |
| D | index.rst | 27 It is very unlikely that an update to :ref:`linux_doc` will be propagated
|
| /linux-5.10/drivers/soc/qcom/ |
| D | smsm.c | 98 * @irq_rising: bitmap tracking if rising bits should be propagated
99 * @irq_falling: bitmap tracking if falling bits should be propagated
100 * @last_value: snapshot of state bits last time the interrupts where propagated
|
| /linux-5.10/arch/x86/mm/ |
| D | pti.c | 128 * tables are not automatically propagated to the usermode tables. in __pti_set_user_pgtbl()
133 * will not be automatically propagated to other mms. in __pti_set_user_pgtbl()
449 * that it's propagated to all mms. in pti_clone_user_shared()
|
| /linux-5.10/fs/xfs/ |
| D | xfs_itable.c | 259 * triggered again and propagated to userspace as there will be no in xfs_bulkstat()
377 * will be triggered again and propagated to userspace as there will be in xfs_inumbers()
|
| /linux-5.10/Documentation/admin-guide/ |
| D | xfs.rst | 400 for a specific class will cause the error to be propagated rather than reset and
403 The action taken by the filesystem when the error is propagated is context
460 to be propagated. The handler configurations are found in the directory:
|
| /linux-5.10/fs/jfs/ |
| D | jfs_umount.c | 101 * ensure all file system file pages are propagated to their in jfs_umount()
|
| /linux-5.10/Documentation/ABI/obsolete/ |
| D | sysfs-class-net-mesh | 49 Defines the bandwidth which is propagated by this
|
| /linux-5.10/net/wimax/ |
| D | op-rfkill.c | 69 * know that the state has changed so it can be properly propagated.
72 * well, as the change is propagated it will come back as a request to
|
| /linux-5.10/arch/arm64/kernel/ |
| D | suspend.c | 118 * to make sure a proper error condition is propagated in cpu_suspend()
|
| /linux-5.10/Documentation/networking/caif/ |
| D | caif.rst | 65 and is blocking further send operation. Flow OFF has been propagated
|
| /linux-5.10/Documentation/block/ |
| D | writeback_cache_control.rst | 55 bits need to be propagated to underlying devices, and a global flush needs
|
123456