| /linux/Documentation/devicetree/ | 
| H A 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/net/tipc/ | 
| H A 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/mm/damon/ | 
| H A D | paddr.c | 155 	phys_addr_t addr, applied;  in damon_pa_pageout()  local 203 	applied = reclaim_pages(&folio_list);  in damon_pa_pageout() 206 	return damon_pa_core_addr(applied * PAGE_SIZE, addr_unit);  in damon_pa_pageout() 214 	phys_addr_t addr, applied = 0;  in damon_pa_mark_accessed_or_deactivate()  local 234 		applied += folio_nr_pages(folio);  in damon_pa_mark_accessed_or_deactivate() 240 	return damon_pa_core_addr(applied * PAGE_SIZE, addr_unit);  in damon_pa_mark_accessed_or_deactivate() 263 	phys_addr_t addr, applied;  in damon_pa_migrate()  local 287 	applied = damon_migrate_pages(&folio_list, s->target_nid);  in damon_pa_migrate() 290 	return damon_pa_core_addr(applied * PAGE_SIZE, addr_unit);  in damon_pa_migrate()
  | 
| /linux/Documentation/mm/damon/ | 
| H A D | design.rst | 379 is recommended.  Note that Parreto principle (80/20 rule) has applied twice. 477 actions are applied to those. 517 the action can be applied within a user-specified time duration. 530 cannot be applied to all regions of interest due to the quotas, DAMOS 661 the scheme's action will be applied to the page regardless of whether it is 663 not anonymous but young, the scheme's action will not be applied, since the 666 matching filter, and the action will be applied to the page. 672         - Applied to pages that belonging to a given address range. 674         - Applied to pages that belonging to a given DAMON monitoring target. 677         - Applied to pages that containing data that not stored in files. [all …] 
 | 
| /linux/drivers/md/dm-vdo/ | 
| H A 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
  | 
| H A 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/Documentation/process/ | 
| H A 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/Documentation/ABI/testing/ | 
| H A 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/Documentation/userspace-api/media/mediactl/ | 
| H A 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/arch/parisc/kernel/ | 
| H A 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/Documentation/devicetree/bindings/firmware/ | 
| H A 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/drivers/platform/x86/amd/pmf/ | 
| H A 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/Documentation/devicetree/bindings/pinctrl/ | 
| H A 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.
  | 
| H A 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.
  | 
| H A 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.
  | 
| H A 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.
  | 
| H A 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.
  | 
| H A D | fsl,imx7d-pinctrl.yaml | 59                 "mux_val" indicates the mux value to be applied. 61                 "input_val" indicates the select input value to be applied. 63                 "pad_setting" indicates the pad configuration value to be applied.
  | 
| /linux/tools/testing/selftests/powerpc/dexcr/ | 
| H A 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/arch/riscv/include/asm/ | 
| H A 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/Documentation/arch/riscv/ | 
| H A 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/drivers/of/unittest-data/ | 
| H A 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/tools/power/cpupower/man/ | 
| H A 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/Documentation/admin-guide/hw-vuln/ | 
| H A D | vmscape.rst | 44 from a malicious guest. This is because Spectre-v2 mitigations are applied at 48 Vulnerability enumeration and mitigation is not applied inside a guest. This is 81    The processor is vulnerable and no mitigation has been applied.
  | 
| /linux/include/dt-bindings/interconnect/ | 
| H A D | qcom,icc.h | 10  * The AMC bucket denotes constraints that are applied to hardware when 11  * icc_set_bw() completes, whereas the WAKE and SLEEP constraints are applied
  |