| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/net/tipc/ |
| D | monitor.c | 69 * @applied: number of reported domain members applied on this monitor list
80 u8 applied; member
187 int applied_aft = peer->applied; in mon_identify_lost_members()
201 /* Start probing if member was removed from applied domain */ in mon_identify_lost_members()
207 /* Member loss is confirmed if it is still in applied domain */ in mon_identify_lost_members()
227 peer->applied = 0; in mon_apply_domain()
233 peer->applied++; in mon_apply_domain()
252 self->applied = member_cnt; in mon_update_local_domain()
304 if (i++ < head->applied) { in mon_assign_roles()
352 peer->applied = 0; in tipc_mon_remove_peer()
[all …]
|
| /kernel/linux/linux-6.6/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 indrect branch prediction barrier after having applied the required
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/arch/parisc/kernel/ |
| D | alternative.c | 26 int index = 0, applied = 0; in apply_alternatives() local
94 applied++; in apply_alternatives()
97 pr_info("%s%salternatives: applied %d out of %d patches\n", in apply_alternatives()
99 applied, index); in apply_alternatives()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/mm/damon/ |
| D | paddr.c | 230 unsigned long addr, applied; in damon_pa_pageout() local
253 applied = reclaim_pages(&folio_list); in damon_pa_pageout()
255 return applied * PAGE_SIZE; in damon_pa_pageout()
261 unsigned long addr, applied = 0; in damon_pa_mark_accessed_or_deactivate() local
276 applied += folio_nr_pages(folio); in damon_pa_mark_accessed_or_deactivate()
280 return applied * PAGE_SIZE; in damon_pa_mark_accessed_or_deactivate()
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-6.6/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,
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| 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,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,imx93-pinctrl.yaml | 53 "mux_val" indicates the mux value to be applied.
55 "input_val" indicates the select input value to be applied.
57 "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,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.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imx8mq-pinctrl.yaml | 50 "mux_val" indicates the mux value to be applied.
52 "input_val" indicates the select input value to be applied.
54 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx8mp-pinctrl.yaml | 50 "mux_val" indicates the mux value to be applied.
52 "input_val" indicates the select input value to be applied.
54 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx8mm-pinctrl.yaml | 50 "mux_val" indicates the mux value to be applied.
52 "input_val" indicates the select input value to be applied.
54 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx8mn-pinctrl.yaml | 50 "mux_val" indicates the mux value to be applied.
52 "input_val" indicates the select input value to be applied.
54 "pad_setting" indicates the pad configuration value to be applied.
|