| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/vpnc/vpnc/ |
| H A D | long-help | 6 conf-variable: IPSec gateway <ip/hostname>
10 conf-variable: IPSec ID <ASCII string>
14 conf-variable: IPSec secret <ASCII string>
18 conf-variable: IPSec obfuscated secret <hex string>
22 conf-variable: Xauth username <ASCII string>
26 conf-variable: Xauth password <ASCII string>
30 conf-variable: Xauth obfuscated password <hex string>
34 conf-variable: Domain <ASCII string>
38 conf-variable: Xauth interactive
43 conf-variable: Vendor <cisco/netscreen>
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | percpu-defs.h | 316 #define __pcpu_size_call_return(stem, variable) \ argument
318 typeof(variable) pscr_ret__; \
319 __verify_pcpu_ptr(&(variable)); \
320 switch(sizeof(variable)) { \
321 case 1: pscr_ret__ = stem##1(variable); break; \
322 case 2: pscr_ret__ = stem##2(variable); break; \
323 case 4: pscr_ret__ = stem##4(variable); break; \
324 case 8: pscr_ret__ = stem##8(variable); break; \
331 #define __pcpu_size_call_return2(stem, variable, ...) \ argument
333 typeof(variable) pscr2_ret__; \
[all …]
|
| /openbmc/webui-vue/docs/.vuepress/components/colors/ |
| H A D | grays.vue | 11 <dt>Color variable:</dt>
12 <dd>${{ color.variable }}</dd>
29 variable: 'gray-100',
34 variable: 'gray-200',
38 variable: 'gray-300',
42 variable: 'gray-400',
46 variable: 'gray-500',
50 variable: 'gray-600',
54 variable: 'gray-700',
58 variable: 'gray-800',
[all …]
|
| H A D | theme.vue | 11 <dt>Color variable:</dt>
15 <dt>Color variable:</dt>
16 <dd>${{ item.variable }}</dd>
30 variable: "blue",
35 variable: "gray-800",
40 variable: 'gray-100',
46 variable: 'gray-900',
51 variable: 'blue',
56 variable: 'green',
61 variable: 'yellow',
[all …]
|
| H A D | all.vue | 16 <dd>{{ item.variable }}</dd>
30 variable: '$blue-500',
35 variable: '$green-500',
40 variable: '$red-500',
45 variable: '$yellow-500',
|
| /openbmc/u-boot/drivers/fastboot/ |
| H A D | fb_getvar.c | 31 const char *variable; member
35 .variable = "version",
38 .variable = "bootloader-version",
41 .variable = "version-bootloader",
44 .variable = "downloadsize",
47 .variable = "max-download-size",
50 .variable = "serialno",
53 .variable = "version-baseband",
56 .variable = "product",
59 .variable = "current-slot",
[all …]
|
| /openbmc/u-boot/lib/efi_loader/ |
| H A D | efi_variable.c | 262 static efi_status_t parse_uboot_variable(char *variable, in parse_uboot_variable() argument
272 guid = strchr(variable, '_'); in parse_uboot_variable()
327 char *native_name, *variable; in efi_get_next_variable_name() local
354 for (variable = efi_variables_list; variable && *variable;) { in efi_get_next_variable_name()
355 if (!strncmp(variable, native_name, name_len) && in efi_get_next_variable_name()
356 variable[name_len] == '=') in efi_get_next_variable_name()
359 variable = strchr(variable, '\n'); in efi_get_next_variable_name()
360 if (variable) in efi_get_next_variable_name()
361 variable++; in efi_get_next_variable_name()
365 if (!(variable && *variable)) in efi_get_next_variable_name()
[all …]
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | shadow-vars.rst | 8 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 …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-firmware-efi-vars | 22 EFI variable flags. Potential values
35 to attain the value of the EFI variable
37 guid: The vendor GUID of the variable. This
39 variable's name.
43 there is to know about the variable.
48 order to update the value of a variable.
62 the variable's value.
73 new variable.
77 variable that has a matching vendor GUID
78 and variable key name.
|
| /openbmc/linux/scripts/kconfig/tests/preprocess/variable/ |
| H A D | Kconfig | 6 # 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.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libssh/libssh/ |
| H A D | 0001-CompilerChecks.cmake-drop-Wunused-variable-flag.patch | 4 Subject: [PATCH] CompilerChecks.cmake: drop -Wunused-variable flag
6 Drop -Wunused-variable flag to fix build with clang:
8 …it/src/threads/libgcrypt.c:29:1: error: unused variable 'gcry_threads_pthread' [-Werror,-Wunused-v…
30 - add_c_compiler_flag("-Werror=unused-variable" SUPPORTED_COMPILER_FLAGS)
31 + #add_c_compiler_flag("-Werror=unused-variable" SUPPORTED_COMPILER_FLAGS)
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables.rst | 23 systems extend the functionality of the variable as it is
42 This variable can be defined to be used by the fetcher to authenticate
58 considerations surrounding this variable:
98 the checksum mechanism. A common example would be the variable for
116 codeparser cache is used (i.e. when calculating variable dependencies for
144 variable, use the following form::
160 BB_DISKMON_WARNINTERVAL variable,
188 variable. This example causes the build system to immediately halt
191 directories are provided with the variable, the build system also
195 defined by the :term:`BB_DISKMON_WARNINTERVAL` variable.
[all …]
|
| H A D | bitbake-user-manual-metadata.rst | 35 it to an empty string, while setting the variable to " " sets it to a
42 variable's value. Doing so allows you to use values that contain the
50 quotes in all other ways. They do not suppress variable expansions.
56 cases where you might find you want to modify an existing variable:
58 - Customize a recipe that uses the variable.
60 - Change a variable's default value used in a ``*.bbclass`` file.
62 - Change the variable in a ``*.bbappend`` file to override the variable
65 - Change the variable in a configuration file so that the value
68 Changing a variable value can sometimes depend on how the value was
70 particular, when you append a value to a variable that has a default
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | variables.rst | 53 To use the variable, list out the package's commands that are also
67 use the :term:`ALTERNATIVE_LINK_NAME` variable to specify the actual
85 duplicated commands. You can use the variable to create a single
101 duplicated commands. You can use the variable to create a single
114 from the :term:`ALTERNATIVE_LINK_NAME` variable.
130 class, this variable identifies a list of distribution features where
143 information on how this variable is used.
151 You can use this variable to create archives of patched source,
153 following variable flags (varflags)::
164 For information on how the variable works, see the
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-secvar | 18 This determines the format of the variable and the accepted
19 format of variable updates.
25 version number in the SB_VERSION variable in the keystore, and
27 "ibm,plpks-sb-unknown" if there is no SB_VERSION variable.
29 What: /sys/firmware/secvar/vars/<variable name>
32 Description: Each secure variable is represented as a directory named as
33 <variable_name>. The variable name is unique and is in ASCII
41 variable. In other words, it represents the size of the data.
46 Description: A read-only file containing the value of the variable. The size
47 of the file represents the maximum size of the variable data.
[all …]
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | sign_rpm.bbclass | 15 # Optional variable for specifying the backend to use for signing.
19 # Optional variable for specifying the algorithm for generating file
22 # Optional variable for the file signing key.
24 # Optional variable for the file signing key password.
26 # Optional variable for specifying the gpg binary/wrapper to use for
29 # Optional variable indicating the number of packages used per gpg
32 # Optional variable for specifying the gnupg "home" directory:
|
| /openbmc/linux/Documentation/trace/ |
| H A D | histogram-design.rst | 89 indicates which type of field it is - key, value, variable, variable
377 map_elt specifically designed to store and retrieve variable values.
378 The diagram below shows those new elements and adds a new variable
379 entry, ts0, corresponding to the ts0 variable in the sched_waking
446 variable. For a normal val hist_field, .flags is just 0 (modulo | | |
447 modifier flags), but if the value is defined as a variable, the .flags | | |
451 into the tracing_map_elts' .vars[] array containing variable values. | | |
452 This idx is used whenever the value of the variable is set or read. | | |
453 The map_elt.vars idx assigned to the given variable is assigned and | | |
465 or val and the .vars[] members point to the value of a variable. The | | |
[all …]
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | kconfig-macro-language.rst | 23 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 …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | device-manager.rst | 25 :term:`USE_DEVFS` variable to "0"
33 variable defines the Device Table to use and should be set in the
35 variable in your ``local.conf`` configuration file.
37 If you do not define the :term:`IMAGE_DEVICE_TABLES` variable, the default
50 variable to "1", which is the default::
57 variable ``CONFIG_DEVTMPFS`` is set when building you build a Linux
65 :term:`VIRTUAL-RUNTIME_dev_manager <VIRTUAL-RUNTIME>` variable in your machine
66 or distro configuration file. Alternatively, you can set this variable in
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/trusted-services/corstone1000/ |
| H A D | 0013-Fix-error-handling-of-variable-index-loading.patch | 4 Subject: [PATCH 3/3] Fix error handling of variable index loading
6 If loading of the variable index from Protected Storage fails, SmmGW
7 will silently continue with empty variable store. This is a serious
33 /* Load the variable index with NV variable info from the persistent store */
67 + IMSG("Index variable does not exist in NV store, continuing with empty index");
71 + EMSG("Loading variable index failed: %d", psa_status);
|
| /openbmc/linux/drivers/net/wireless/intersil/hostap/ |
| H A D | hostap_80211.h | 22 u8 variable[0]; member
31 u8 variable[0]; member
38 u8 variable[0]; member
45 u8 variable[0]; member
58 u8 variable[0]; member
|
| /openbmc/openbmc/poky/meta/recipes-devtools/tcltk8/tcl8/ |
| H A D | interp.patch | 20 variable result
26 variable done {}
28 - after 10 [list ::set [namespace which -variable done] {}]
29 - vwait [namespace which -variable done]
35 variable result {}
|
| /openbmc/openbmc/poky/meta/recipes-devtools/tcltk/tcl/ |
| H A D | 0005-tcl-fix-race-in-interp.test.patch | 20 variable result
26 variable done {}
28 - after 10 [list ::set [namespace which -variable done] {}]
29 - vwait [namespace which -variable done]
35 variable result {}
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci-jobs.rst.inc | 8 Set variable globally in the user's CI namespace
15 https://docs.gitlab.com/ee/ci/variables/#add-a-cicd-variable-to-a-project
17 Set variable manually when pushing a branch or tag to the user's repository
23 Example setting the QEMU_CI_EXAMPLE_VAR variable:
27 git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
41 git config --local alias.push-ci "push -o ci.variable=QEMU_CI=1"
42 git config --local alias.push-ci-now "push -o ci.variable=QEMU_CI=2"
146 Set this variable to 1 to create the pipelines, but leave all
149 Set this variable to 2 to create the pipelines and run all
157 reach the timeout limit). Set this variable to have the tests using the
[all …]
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 43 are included. Including a variable in the value of
57 useful if you want to set a variable value just for the SDK and not the
68 :term:`INHERIT` variable and you
71 variable as described in the previous section.
99 variable as described in the previous section.
110 variable. For more information, see the
131 :term:`COREBASE_FILES` variable as previously described.
137 :term:`SDK_TITLE` variable and then
144 set. If the :term:`DISTRO_NAME` variable is not set, the title is derived
145 from the :term:`DISTRO` variable.
[all …]
|