| /openbmc/intel-ipmi-oem/include/ |
| H A D | biosxml.hpp | 378 std::stack<knob::DepexOperators>& operators, in evaluateExprStack() argument
381 if (values.size() != (operators.size() + 1)) in evaluateExprStack()
386 while (!operators.empty()) in evaluateExprStack()
394 switch (operators.top()) in evaluateExprStack()
476 operators.pop(); in evaluateExprStack()
507 std::stack<knob::DepexOperators> operators; in evaluateExpression() local
533 if (!operators.empty()) in evaluateExpression()
535 if (!evaluateExprStack(values, operators, value)) in evaluateExpression()
543 operators.emplace(knob::DepexOperators::OR); in evaluateExpression()
551 if (!operators.empty()) in evaluateExpression()
[all …]
|
| /openbmc/linux/drivers/scsi/ |
| H A D | script_asm.pl | 69 %operators = (
76 %operators = (
602 $code[$address] |= $operators{$op};
605 $code[$address] |= $operators{$op};
|
| /openbmc/u-boot/doc/ |
| H A D | README.commands.itest | 4 Now table driven to allow the operators
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-4.0.rst | 196 :append/:prepend in combination with other operators
199 The ``append``, ``prepend`` and ``remove`` operators can now only be combined with
200 ``=`` and ``:=`` operators. To the exception of the ``append`` plus ``+=`` and
203 confusion on how the override style syntax operators work and should be used.
208 the same behavior. You can learn more about override style syntax operators
|
| H A D | release-notes-3.4.1.rst | 28 - bitbake: Revert "parse/ast: Show errors for append/prepend/remove operators combined with +=/.="
41 - bitbake: parse/ast: Show errors for append/prepend/remove operators combined with +=/.=
|
| H A D | migration-1.8.rst | 163 multiple licenses are specified with no operators to specify how the
|
| /openbmc/linux/scripts/coccinelle/misc/ |
| H A D | boolconv.cocci | 4 //# Relational and logical operators evaluate to bool,
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/octave/ |
| H A D | octave_7.2.0.bb | 47 for folder in "liboctave/operators liboctave/numeric liboctave/array liboctave/util"; do
|
| /openbmc/qemu/target/hexagon/idef-parser/ |
| H A D | macros.h.inc | 117 /* Unary operators */
120 /* Binary operators */
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-metadata.rst | 11 describes the available syntax and operators as well as provides
200 assignment operators. The "??=" operator takes effect immediately, replacing
264 the "+=" and "=+" operators. These operators insert a space between the
267 These operators take immediate effect during parsing. Here are some
284 the ".=" and "=." operators.
286 These operators take immediate effect during parsing. Here are some
303 These operators differ from the ":=", ".=", "=.", "+=", and "=+"
304 operators in that their effects are applied at variable expansion time
385 ":remove" as compared to the "+=" and "=+" operators is that the
386 override style operators provide guaranteed operations. For example,
[all …]
|
| /openbmc/linux/sound/drivers/opl3/ |
| H A D | opl3_oss.c | 212 sbi.operators); in snd_opl3_load_patch_seq_oss()
|
| /openbmc/docs/designs/ |
| H A D | redfish-pcie.md | 29 administrators and operators.
|
| /openbmc/docs/ |
| H A D | cpp-style-and-conventions.md | 389 - Insert whitespace around binary operators for readability.
396 - Do not insert whitespace around unary operators.
417 - Prefer line-breaks after operators to show continuation.
|
| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A D | using-gpio.rst | 26 operators to have a deep knowledge of the equipment and knows about the
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | method-customizing.rst | 27 declared inside scope operators are also not supported.
|
| /openbmc/linux/tools/testing/selftests/bpf/ |
| H A D | veristat.c | 443 } operators[] = { variable
485 for (i = 0; i < ARRAY_SIZE(operators); i++) { in append_filter()
492 op_str = operators[i].op_str; in append_filter()
535 f->op = operators[i].op_kind; in append_filter()
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | rcu_dereference.rst | 56 operators. For example, for a given variable "x", avoid
74 - Do not use the results from relational operators ("==", "!=",
88 As before, the reason this is buggy is that relational operators
|
| /openbmc/linux/Documentation/driver-api/mtd/ |
| H A D | nand_ecc.rst | 172 C does have bitwise operators but not really operators to do the above
407 with only a single statement and by using operators like ^=
700 Change the lookup using the parity array by using shift operators (e.g.
|
| /openbmc/qemu/docs/devel/ |
| H A D | writing-monitor-commands.rst | 357 machines, as opposed to exclusively human operators.
360 for human operators. While they may return large amounts of formatted
544 useful only to human operators.
|
| /openbmc/qemu/docs/specs/ |
| H A D | vmgenid.rst | 88 * Disassembling to symbolic ASL+ operators
|
| /openbmc/linux/Documentation/process/ |
| H A D | coding-style.rst | 274 Use one space around (on each side of) most binary and ternary operators,
279 but no space after unary operators::
283 no space before the postfix increment & decrement unary operators::
287 no space after the prefix increment & decrement unary operators::
291 and no space around the ``.`` and ``->`` structure member operators.
|
| /openbmc/linux/Documentation/trace/ |
| H A D | events.rst | 169 combined using the logical operators '&&' and '||'. A predicate is
178 operators as shell metacharacters.
183 The relational-operators depend on the type of the field being tested:
185 The operators available for numeric fields are:
|
| H A D | fprobetrace.rst | 117 The field access operators, ``->`` and ``.`` can be combined for accessing deeper
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | cpumasks.rst | 286 bitwise operators (and queried).
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | soundcard.h | 477 sbi_instr_data operators; /* Register settings for operator cells (.SBI format) */ member
|