Home
last modified time | relevance | path

Searched refs:variable (Results 1 – 25 of 581) sorted by relevance

12345678910>>...24

/Linux-v5.4/include/linux/
Dpercpu-defs.h317 #define __pcpu_size_call_return(stem, variable) \ argument
319 typeof(variable) pscr_ret__; \
320 __verify_pcpu_ptr(&(variable)); \
321 switch(sizeof(variable)) { \
322 case 1: pscr_ret__ = stem##1(variable); break; \
323 case 2: pscr_ret__ = stem##2(variable); break; \
324 case 4: pscr_ret__ = stem##4(variable); break; \
325 case 8: pscr_ret__ = stem##8(variable); break; \
332 #define __pcpu_size_call_return2(stem, variable, ...) \ argument
334 typeof(variable) pscr2_ret__; \
[all …]
Dieee80211.h905 u8 variable[0]; member
914 u8 variable[0]; member
921 u8 variable[0]; member
928 u8 variable[0]; member
939 u8 variable[0]; member
943 u8 variable[0]; member
951 u8 variable[0]; member
960 u8 variable[0]; member
964 u8 variable[0]; member
969 u8 variable[0]; member
[all …]
/Linux-v5.4/Documentation/livepatch/
Dshadow-vars.rst8 unmodified. The shadow variable API described in this document is used
14 used to describe shadow variable version, class or type, etc. More
29 * The klp_shadow variable data structure encapsulates both tracking
40 klp_shadow_get_or_alloc() are zeroing the variable by default.
46 to do actions that can be done only once when a new variable is allocated.
48 * klp_shadow_get() - retrieve a shadow variable data pointer
51 * klp_shadow_alloc() - allocate and add a new shadow variable
60 - allocate a new shadow variable
61 - initialize the variable using a custom constructor and data when provided
64 * klp_shadow_get_or_alloc() - get existing or alloc a new shadow variable
[all …]
/Linux-v5.4/scripts/kconfig/tests/preprocess/variable/
DKconfig6 # Simply expanded variable.
12 # Recursively expanded variable.
18 # Append something to a simply expanded variable.
24 # Append something to a recursively expanded variable.
30 # Use += operator to an undefined variable.
31 # This works as a recursively expanded variable.
37 # You can use variable references for the lefthand side of assignment statement.
/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars21 EFI variable flags. Potential values
34 to attain the value of the EFI variable
36 guid: The vendor GUID of the variable. This
38 variable's name.
42 there is to know about the variable.
47 order to update the value of a variable.
61 the variable's value.
70 new variable.
74 variable that has a matching vendor GUID
75 and variable key name.
/Linux-v5.4/Documentation/kbuild/
Dkconfig-macro-language.rst23 The macro language replaces the variable references with their expanded form,
53 Like in Make, a variable in Kconfig works as a macro variable. A macro
54 variable is expanded "in place" to yield a text string that may then be
55 expanded further. To get the value of a variable, enclose the variable name in
56 $( ). The parentheses are required even for single-letter variable names; $X is
62 A simply expanded variable is defined using the := assignment operator. Its
66 A recursively expanded variable is defined using the = assignment operator.
67 Its righthand side is simply stored as the value of the variable without
68 expanding it in any way. Instead, the expansion is performed when the variable
72 variable. The righthand side of += is expanded immediately if the lefthand
[all …]
Dkconfig.rst41 This environment variable can be used to specify a default kernel config
66 use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
81 (usually a subset of all) preset config symbols. These variable
112 This variable can be used to skew the probabilities. This variable can
149 If this variable has a non-blank value, it prevents silent kernel
154 This environment variable can be set to specify the path & name of the
159 This environment variable can be set to specify the path & name of the
164 This environment variable can be set to specify the path & name of the
216 It is possible to select different color themes using the variable
/Linux-v5.4/drivers/net/wireless/intersil/hostap/
Dhostap_80211.h22 u8 variable[0]; member
31 u8 variable[0]; member
38 u8 variable[0]; member
45 u8 variable[0]; member
58 u8 variable[0]; member
/Linux-v5.4/scripts/coccinelle/misc/
Dboolinit.cocci159 cocci.print_main("WARNING: Comparison of 0/1 to bool variable",p)
165 cocci.print_main("WARNING: Assignment of 0/1 to bool variable",p1)
171 cocci.print_main("ERROR: Assignment of non-0/1 constant to bool variable",p2)
183 coccilib.report.print_report(p[0],"WARNING: Comparison of 0/1 to bool variable")
189 coccilib.report.print_report(p1[0],"WARNING: Assignment of 0/1 to bool variable")
195 coccilib.report.print_report(p2[0],"ERROR: Assignment of non-0/1 constant to bool variable")
Difaddr.cocci2 /// The address of a variable or field is likely always to be non-zero.
28 cocci.print_main("test of a variable/field address",p)
34 msg = "ERROR: test of a variable/field address"
Dreturnvar.cocci3 /// Remove unneeded variable used to store return value.
58 coccilib.report.print_report(p1[0], "Unneeded variable: \"" + ret + "\". Return \"" + C + "\" on li…
66 cocci.print_main("unneeded \"" + ret + "\" variable", p1)
/Linux-v5.4/Documentation/devicetree/bindings/clock/
Darm-syscon-icst.txt22 Integrator/AP 22 1 Bit 8 0, rest variable
25 Integrator/AP 46 3 Bit 8 0, rest variable
31 Integrator/CP 22 variable Bit 8 0, rest variable
34 Integrator/CP 22 variable Bit 8 0, rest variable
/Linux-v5.4/Documentation/networking/
Dnetif-msg.txt15 integer variable that controls the debug message level. The message
30 Initially this message level variable was uniquely named in each driver
47 Retaining the per-driver integer variable "debug" as a module
50 Adding a per-interface private variable named "msg_enable". The
51 variable is a bit map rather than a level, and is initialized as
/Linux-v5.4/scripts/kconfig/
Dpreprocess.c231 struct variable { struct
239 static struct variable *variable_lookup(const char *name) in variable_lookup() argument
241 struct variable *v; in variable_lookup()
253 struct variable *v; in variable_expand()
282 struct variable *v; in variable_add()
324 static void variable_del(struct variable *v) in variable_del()
334 struct variable *v, *tmp; in variable_all_del()
/Linux-v5.4/security/
DKconfig.hardening8 stack variable initializations, this warning is silenced for
45 Disable automatic stack variable initialization.
47 classes of uninitialized stack variable exploits
57 uninitialized stack variable exploits and information
70 of uninitialized stack variable exploits and information
88 of uninitialized stack variable exploits and information
97 of uninitialized stack variable exploits and information
109 structleak plugin finds a variable it thinks needs to be
122 potential for uninitialized stack variable exploits or information
125 most uninitialized stack variable attacks, with the performance
/Linux-v5.4/tools/memory-model/litmus-tests/
DCoRW+poonceonce+Once.litmus7 * a given variable and a later write to that same variable are ordered.
DCoWR+poonceonce+Once.litmus7 * given variable and a later read from that same variable are ordered.
/Linux-v5.4/fs/efivarfs/
DKconfig8 variable support via sysfs, as it doesn't suffer from the
9 same 1024-byte variable size limit.
/Linux-v5.4/drivers/staging/rtl8723bs/include/
Drtl8723b_hal.h258 void SetHwReg8723B(struct adapter *padapter, u8 variable, u8 *val);
259 void GetHwReg8723B(struct adapter *padapter, u8 variable, u8 *val);
260 u8 SetHalDefVar8723B(struct adapter *padapter, enum HAL_DEF_VARIABLE variable,
262 u8 GetHalDefVar8723B(struct adapter *padapter, enum HAL_DEF_VARIABLE variable,
Dhal_com.h240 void SetHwReg(struct adapter *padapter, u8 variable, u8 *val);
241 void GetHwReg(struct adapter *padapter, u8 variable, u8 *val);
244 u8 SetHalDefVar(struct adapter *adapter, enum HAL_DEF_VARIABLE variable,
246 u8 GetHalDefVar(struct adapter *adapter, enum HAL_DEF_VARIABLE variable,
/Linux-v5.4/Documentation/media/uapi/v4l/
Dvidioc-g-priority.rst47 variable where the driver stores the current priority.
50 an enum v4l2_priority variable and call :ref:`VIDIOC_S_PRIORITY <VIDIOC_G_PRIORITY>` ioctl
51 with a pointer to this variable.
92 On success 0 is returned, on error -1 and the ``errno`` variable is set
/Linux-v5.4/Documentation/core-api/
Dlocal_ops.rst39 Local atomic operations only guarantee variable modification atomicity wrt the
72 different CPU between getting the per-cpu variable and doing the
79 * Reading the local cpu variable will provide the current copy of the
80 variable.
84 variable can be read when reading some *other* cpu's variables.
105 access to the per cpu variable. For instance::
131 the ``local_t`` variable as a counter of bytes written in a buffer: there should
160 /* This is what incrementing the variable would look like within a
/Linux-v5.4/Documentation/devicetree/bindings/net/
Dsamsung-sxgbe.txt7 These interrupts are ordered by fixed and follows variable
11 index 1 to 25 - 8 variable trasmit interrupts, variable 16 receive interrupts
/Linux-v5.4/Documentation/admin-guide/acpi/
Dssdt-overlays.rst108 In order to load SSDTs from an EFI variable the efivar_ssdt kernel command line
109 parameter can be used. The argument for the option is the variable name to
113 In order to store the AML code in an EFI variable the efivarfs filesystem can be
118 EFI variable. Updating a file in /sys/firmware/efi/efivars will update the EFI
119 variable. Please note that the file name needs to be specially formatted as
121 represent the attributes of the EFI variable (see EFI_VARIABLE_MASK in
126 variable with the content from a given file::
/Linux-v5.4/drivers/net/wireless/realtek/rtlwifi/rtl8723be/
Dhw.h7 void rtl8723be_get_hw_reg(struct ieee80211_hw *hw, u8 variable, u8 *val);
24 void rtl8723be_set_hw_reg(struct ieee80211_hw *hw, u8 variable, u8 *val);

12345678910>>...24