| /Linux-v5.10/drivers/net/wireguard/ |
| D | allowedips.c | 72 #define REF(p) rcu_access_pointer(p) in walk_remove_by_peer() macro
83 if (unlikely(!peer || !REF(*top))) in walk_remove_by_peer()
93 if (!prev || REF(prev->bit[0]) == node || in walk_remove_by_peer()
94 REF(prev->bit[1]) == node) { in walk_remove_by_peer()
95 if (REF(node->bit[0])) in walk_remove_by_peer()
97 else if (REF(node->bit[1])) in walk_remove_by_peer()
99 } else if (REF(node->bit[0]) == prev) { in walk_remove_by_peer()
100 if (REF(node->bit[1])) in walk_remove_by_peer()
109 &node->bit[!REF(node->bit[0])])); in walk_remove_by_peer()
118 #undef REF in walk_remove_by_peer()
|
| /Linux-v5.10/Documentation/devicetree/bindings/iio/dac/ |
| D | ad7303.txt | 10 - REF-supply: Phandle to the external reference voltage supply. This should
11 only be set if there is an external reference voltage connected to the REF
22 REF-supply = <&vref_supply>;
|
| /Linux-v5.10/arch/sh/kernel/cpu/sh3/ |
| D | setup-sh770x.c | 32 RTC, WDT, REF, enumerator
43 INTC_VECT(REF, 0x580),
44 INTC_VECT(REF, 0x5a0),
69 { 0xfffffee4, 0, 16, 4, /* IPRB */ { WDT, REF, SCI, 0 } },
|
| D | setup-sh7710.c | 28 RTC, WDT, REF, enumerator
54 INTC_VECT(REF, 0x580),
59 { 0xfffffee4, 0, 16, 4, /* IPRB */ { WDT, REF, 0, 0 } },
|
| /Linux-v5.10/arch/sh/kernel/cpu/sh4/ |
| D | setup-sh7750.c | 185 TMU3, TMU4, TMU0, TMU1, TMU2, RTC, SCI1, SCIF, WDT, REF, enumerator
202 INTC_VECT(REF, 0x580), INTC_VECT(REF, 0x5a0),
207 { 0xffd00008, 0, 16, 4, /* IPRB */ { WDT, REF, SCI1, 0 } },
|
| D | setup-sh7760.c | 37 WDT, REF, enumerator
75 INTC_VECT(REF, 0x580), INTC_VECT(REF, 0x5a0),
105 { 0xffd00008, 0, 16, 4, /* IPRB */ { WDT, REF, 0, 0 } },
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | path-lookup.rst | 30 will allow us to review "REF-walk" and "RCU-walk" separately. But we
142 REF-walk: simple concurrency management with refcounts and spinlocks
148 pathname, and focus on the "REF-walk" approach to concurrency
155 REF-walk is fairly heavy-handed with locks and reference counts. Not
162 The locking mechanisms used by REF-walk include:
205 When looking for a name in a directory, REF-walk takes ``d_lock`` on
211 REF-walk can take ``d_lock`` to get a stable reference to ``d_parent``,
517 Apart from symbolic links, there are only two parts of the "REF-walk"
600 It is in many ways similar to REF-walk and the two share quite a bit
604 We noted that REF-walk is complex because there are numerous details
[all …]
|
| D | ubifs-authentication.rst | 171 / CS | REF | REF | | \ \ DENT | INO | INO | /
182 (CS) and reference nodes (REF) pointing to main area
344 ,.REF#0,-> bud -> bud -> bud.-> auth -> bud -> bud.-> auth ...
351 , REF#1 -> bud -> bud,-> auth ...
354 REF#2 -> ...
|
| D | autofs.rst | 173 to "REF-walk", which is slower but more robust.
189 mounted, it *will* fall back to REF-walk. `d_manage()` cannot make the
|
| /Linux-v5.10/scripts/gcc-plugins/ |
| D | gcc-common.h | 185 #define PASS_INFO(NAME, REF, ID, POS) \ argument
188 .reference_pass_name = REF, \
|
| /Linux-v5.10/include/linux/ |
| D | property.h | 316 REF, _val_, _len_)
|
