| /linux-6.12.1/Documentation/devicetree/ |
| D | changesets.rst | 9 will be applied, or none of them will be. If an error occurs partway
12 applied.
14 When a changeset is applied, all of the changes get applied to the tree
31 entire changeset will get applied, or if there is an error the tree will
36 If a successfully applied changeset needs to be removed, it can be done
|
| /linux-6.12.1/net/tipc/ |
| D | monitor.c | 69 * @applied: number of reported domain members applied on this monitor list
80 u8 applied; member
217 int applied_aft = peer->applied; in mon_identify_lost_members()
231 /* Start probing if member was removed from applied domain */ in mon_identify_lost_members()
237 /* Member loss is confirmed if it is still in applied domain */ in mon_identify_lost_members()
257 peer->applied = 0; in mon_apply_domain()
263 peer->applied++; in mon_apply_domain()
282 self->applied = member_cnt; in mon_update_local_domain()
334 if (i++ < head->applied) { in mon_assign_roles()
382 peer->applied = 0; in tipc_mon_remove_peer()
[all …]
|
| /linux-6.12.1/drivers/md/dm-vdo/ |
| D | action-manager.h | 26 * an optional method to be applied to each of the zones
29 * applied to all zones
37 * A function which is to be applied asynchronously to a set of zones.
39 * @zone_number: The number of zone to which the action is being applied
46 * A function which is to be applied asynchronously on an action manager's initiator thread as the
|
| D | action-manager.c | 21 * @preamble: The method to run on the initiator thread before the action is applied to each zone.
23 * @conclusion: The method to run on the initiator thread after the action is applied to each zone.
45 * @zones: The number of zones in which an action is to be applied.
92 * @zones: The number of zones to which actions will be applied.
276 * vdo_schedule_action() - Schedule an action to be applied to all zones.
282 * applied to all zones; may be NULL.
302 * vdo_schedule_operation() - Schedule an operation to be applied to all zones.
309 * applied to all zones; may be NULL.
338 * applied to all zones; may be NULL.
|
| /linux-6.12.1/Documentation/process/ |
| D | applying-patches.rst | 16 one of the many trees/branches should be applied to. Hopefully this document
57 To revert a previously applied patch, use the -R argument to patch.
58 So, if you applied a patch like this::
134 it'll tell you about it by saying the patch applied with **fuzz**.
141 read this file to see exactly what change couldn't be applied, so you can
144 If you don't have any third-party patches applied to your kernel source, but
158 applied with ``-p0`` instead of ``-p1`` (reading the patch file should reveal if
174 patch could not be applied correctly and the patch program was unable to
179 If you get ``Reversed (or previously applied) patch detected! Assume -R? [n]``
183 If you actually did apply this patch previously and you just re-applied it
[all …]
|
| /linux-6.12.1/mm/damon/ |
| D | paddr.c | 248 unsigned long addr, applied; in damon_pa_pageout() local
289 applied = reclaim_pages(&folio_list); in damon_pa_pageout()
291 return applied * PAGE_SIZE; in damon_pa_pageout()
297 unsigned long addr, applied = 0; in damon_pa_mark_accessed_or_deactivate() local
312 applied += folio_nr_pages(folio); in damon_pa_mark_accessed_or_deactivate()
316 return applied * PAGE_SIZE; in damon_pa_mark_accessed_or_deactivate()
454 unsigned long addr, applied; in damon_pa_migrate() local
472 applied = damon_pa_migrate_pages(&folio_list, s->target_nid); in damon_pa_migrate()
474 return applied * PAGE_SIZE; in damon_pa_migrate()
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-dac-ad5766 | 11 Inverts the dither applied to the selected DAC channel. Dither is not
24 Scales the dither before it is applied to the selected channel.
30 Selects dither source applied to the selected channel. Write "0" to
|
| /linux-6.12.1/Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 13 Another is support of stateless codecs, which require controls to be applied
30 applied when needed to get the expected result. Configuration values at the time
56 fact that the ioctl is part of said request, and is not to be applied
59 instead of being immediately applied, and buffers queued to a request do not
76 may synchronize so the requested pipeline's topology is applied before the
89 Controls can still be set without a request and are applied immediately,
134 be applied by the driver for the OUTPUT buffer, allowing user-space
|
| /linux-6.12.1/Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 51 The processor is vulnerable and no mitigations have been applied.
56 functionality to address the vulnerability has been applied.
60 The "Safe RET" mitigation (see below) has been applied to protect the
61 kernel, but the IBPB-extending microcode has not been applied. User
66 Extended IBPB functionality microcode patch has been applied. It does
138 an indirect branch prediction barrier after having applied the required
|
| /linux-6.12.1/Documentation/devicetree/bindings/firmware/ |
| D | nxp,imx95-scmi-pinctrl.yaml | 44 "mux_val" indicates the mux value to be applied.
46 "input_val" indicates the select input value to be applied.
48 "pad_setting" indicates the pad configuration value to be applied.
|
| /linux-6.12.1/include/linux/ |
| D | netfilter_netdev.h | 67 * @dev: netdev whose egress hooks shall be applied to @skb
75 * When tc redirects a packet to another interface, netfilter is not applied
78 * The nf_skip_egress flag controls whether netfilter is applied on egress.
82 * false after sch_handle_egress(). This ensures that netfilter is applied
|
| /linux-6.12.1/arch/parisc/kernel/ |
| D | alternative.c | 27 int index = 0, applied = 0; in apply_alternatives() local
96 applied++; in apply_alternatives()
99 pr_info("%s%salternatives: applied %d out of %d patches\n", in apply_alternatives()
101 applied, index); in apply_alternatives()
|
| /linux-6.12.1/tools/power/cpupower/man/ |
| D | cpupower-set.1 | 14 are applied on all cores. How to modify single core configurations is
16 option affects the whole system or can be applied to individual cores is
48 This option can be applied to individual cores only via the \-\-cpu option,
|
| /linux-6.12.1/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imxrt1050.yaml | 51 "mux_val" indicates the mux value to be applied.
53 "input_val" indicates the select input value to be applied.
55 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx8ulp-pinctrl.yaml | 48 "mux_mode" indicates the mux value to be applied.
50 "input_val" indicates the select input value to be applied.
52 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imxrt1170.yaml | 51 "mux_val" indicates the mux value to be applied.
53 "input_val" indicates the select input value to be applied.
55 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx9-pinctrl.yaml | 55 "mux_val" indicates the mux value to be applied.
57 "input_val" indicates the select input value to be applied.
59 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx8m-pinctrl.yaml | 55 "mux_val" indicates the mux value to be applied.
57 "input_val" indicates the select input value to be applied.
60 applied.
|
| /linux-6.12.1/arch/riscv/include/asm/ |
| D | alternative.h | 24 #define RISCV_ALTERNATIVES_BOOT 0 /* alternatives applied during regular boot */
25 #define RISCV_ALTERNATIVES_MODULE 1 /* alternatives applied during module-init */
26 #define RISCV_ALTERNATIVES_EARLY_BOOT 2 /* alternatives applied before mmu start */
|
| /linux-6.12.1/tools/testing/selftests/powerpc/dexcr/ |
| D | dexcr_test.c | 24 "setting aspect across exec not applied"); in dexcr_prctl_onexec_test_child()
32 "clearing aspect across exec not applied"); in dexcr_prctl_onexec_test_child()
126 /* Verify the onexec value is applied across exec */ in dexcr_prctl_aspect_test()
139 "setting aspect on exec wrongly applied to fork"); in dexcr_prctl_aspect_test()
161 "clearing aspect on exec wrongly applied to fork"); in dexcr_prctl_aspect_test()
|
| /linux-6.12.1/drivers/platform/x86/amd/pmf/ |
| D | auto-mode.c | 173 !config_store.transition[i].applied) { in amd_pmf_trans_automode()
174 config_store.transition[i].applied = true; in amd_pmf_trans_automode()
178 config_store.transition[i].applied) { in amd_pmf_trans_automode()
179 config_store.transition[i].applied = false; in amd_pmf_trans_automode()
204 config_store.transition[0].applied, in amd_pmf_trans_automode()
205 config_store.transition[1].applied, in amd_pmf_trans_automode()
206 config_store.transition[2].applied, in amd_pmf_trans_automode()
207 config_store.transition[3].applied); in amd_pmf_trans_automode()
213 if (config_store.transition[j].applied) { in amd_pmf_trans_automode()
|
| /linux-6.12.1/Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 27 likely either requested changes, or expect it to be applied to another tree.
33 The exact commit to which a series has been applied will be noted on patchwork.
34 Patches for which any of the checks fail are unlikely to be applied and in most
|
| /linux-6.12.1/drivers/of/unittest-data/ |
| D | Makefile | 52 # the overlays can be applied successfully by fdtoverlay. This does not
53 # guarantee that the overlays can be applied successfully at run time by
57 # The overlays are applied on top of static_base_1.dtb and static_base_2.dtb to
|
| /linux-6.12.1/drivers/fpga/ |
| D | of-fpga-region.c | 181 * of_fpga_region_parse_ov - parse and check overlay applied to region
184 * @overlay: overlay applied to the FPGA region
186 * Given an overlay applied to an FPGA region, parse the FPGA image specific
204 dev_err(dev, "Region already has overlay applied.\n"); in of_fpga_region_parse_ov()
275 * @region: FPGA region that the overlay was applied to
278 * Called when an overlay targeted to an FPGA Region is about to be applied.
302 dev_err(dev, "Region already has overlay applied.\n"); in of_fpga_region_notify_pre_apply()
|
| /linux-6.12.1/drivers/staging/media/atomisp/pci/ |
| D | ia_css_types.h | 154 * Before the shading correction is applied, NxN-filter and/or scaling
155 * are applied in the isp, depending on the isp binaries.
162 * Shading correction is applied to the area
174 …* The shading correction is applied to the bayer area which contains sensor data and padding data.
182 * In some isp binaries, the bayer scaling is applied before the shading correction is applied.
191 * This is the size BEFORE the bayer scaling is applied.
196 * The size of this area assumes the size AFTER the bayer scaling is applied
344 are applied to the physical sensor data area.
601 *output_frame; /** Output frame the config is to be applied to (optional) */
602 …u32 isp_config_id; /** Unique ID to track which config was actually applied to a particular fram…
|