| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/7zip/bit7z/ |
| H A D | 0001-Fix-tests-with-musl.patch | 16 @@ -49,6 +49,8 @@ constexpr PortableErrorTest hresult_tests[] = { // NOLINT(*-avoid-c-arrays)
25 @@ -67,6 +69,8 @@ constexpr PortableErrorTest hresult_tests[] = { // NOLINT(*-avoid-c-arrays)
34 @@ -74,6 +78,8 @@ constexpr PortableErrorTest hresult_tests[] = { // NOLINT(*-avoid-c-arrays)
43 @@ -81,6 +87,8 @@ constexpr PortableErrorTest hresult_tests[] = { // NOLINT(*-avoid-c-arrays)
|
| /openbmc/webui-vue/src/utilities/ |
| H A D | objectUtils.js | 2 * Deeply merge two plain objects (or arrays) without mutating the inputs.
5 * - Arrays from the source replace arrays on the target.
|
| /openbmc/phosphor-led-sysfs/ |
| H A D | argument.hpp | 31 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
38 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
46 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
|
| H A D | argument.cpp | 28 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
62 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-bitarray_3.4.1.bb | 1 SUMMARY = "efficient arrays of booleans -- C extension"
2 DESCRIPTION = "A high-level Python efficient arrays of booleans -- C extension"
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/intel/Protocol/PECI/ |
| H A D | Raw.interface.yaml | 16 An array of byte arrays where each byte array holds the raw
23 An array of byte arrays where each byte array holds the raw
|
| /openbmc/qemu/util/ |
| H A D | fdmon-poll.c | 18 * Stack-allocated arrays would be perfect but they have size limitations;
19 * heap allocation is expensive enough that we want to reuse arrays across
21 * any lock, the arrays cannot be stored in AioContext. Thread-local data
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ActionInfo.v1_5_0.json | 127 …ues for numbers and durations' clause of the Redfish Specification. For arrays, this property sha…
134 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
150 …l appear in the same array order as the `AllowableValues` property. For arrays, this property sha…
163 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
212 …roperty shall contain the maximum value that this service supports. For arrays, this property sha…
222 …roperty shall contain the minimum value that this service supports. For arrays, this property sha…
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ActionInfo.v1_5_0.json | 127 …ues for numbers and durations' clause of the Redfish Specification. For arrays, this property sha…
134 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
150 …l appear in the same array order as the `AllowableValues` property. For arrays, this property sha…
163 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
212 …roperty shall contain the maximum value that this service supports. For arrays, this property sha…
222 …roperty shall contain the minimum value that this service supports. For arrays, this property sha…
|
| /openbmc/openbmc-tools/tracing/ |
| H A D | trace | 34 # Look Ma! Associative arrays in ash!
45 # fake associative arrays
|
| /openbmc/u-boot/include/ |
| H A D | linker_lists.h | 5 * Implementation of linker-generated arrays
41 * generated arrays. The user is expected to build their own macro wrapper
103 * thing: zero-sized arrays, which are both 0-byte-size and exempt from
220 * Since this macro defines the start of the linker-generated arrays,
243 * Since this macro defines the end of the linker-generated arrays,
|
| H A D | ubispl.h | 14 * (static) volume to size the ubispl internal arrays.
24 * ubispl internal arrays.
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libenv/ |
| H A D | libenv-perl_1.04.bb | 1 SUMMARY = "Perl module that imports environment variables as scalars or arrays"
|
| /openbmc/openbmc/poky/meta/recipes-bsp/grub/files/ |
| H A D | CVE-2025-0678_CVE-2025-1125.patch | 4 Subject: [PATCH] fs: Prevent overflows when allocating memory for arrays
6 Use grub_calloc() when allocating memory for arrays to ensure proper
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libio/ |
| H A D | libio-stringy-perl_2.111.bb | 1 SUMMARY = "IO-stringy - I/O on in-core objects like strings and arrays"
|
| /openbmc/openbmc/poky/meta/recipes-devtools/orc/ |
| H A D | orc_0.4.41.bb | 3 …s for compiling and executing SIMD assembly language-like programs that operate on arrays of data."
|
| /openbmc/qemu/hw/ppc/ |
| H A D | spapr_numa.c | 168 * - all associativity arrays were initialized with their own in spapr_numa_define_FORM1_domains()
269 * For all associativity arrays: first position is the size, in spapr_numa_FORM1_affinity_init()
316 * For all resources but CPUs, FORM2 associativity arrays will in spapr_numa_FORM2_affinity_init()
321 * CPUs will write an additional 'vcpu_id' on top of the arrays in spapr_numa_FORM2_affinity_init()
409 /* ibm,associativity-lookup-arrays */ in spapr_numa_write_assoc_lookup_arrays()
427 return fdt_setprop(fdt, offset, "ibm,associativity-lookup-arrays", in spapr_numa_write_assoc_lookup_arrays()
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | ActionInfo_v1.xml | 96 <Annotation Term="OData.LongDescription" String="This property shall indicate the allowable values for this parameter as applied to this action target. For arrays, this property shall represent the allowable values for each array member."/>
183 <Annotation Term="OData.LongDescription" String="This integer or number property shall contain the minimum value that this service supports. For arrays, this property shall represent the minimum value for each array member. This property shall not be present for non-integer or number parameters."/>
188 <Annotation Term="OData.LongDescription" String="This integer or number property shall contain the maximum value that this service supports. For arrays, this property shall represent the maximum value for each array member. This property shall not be present for non-integer or number parameters."/>
253 <Annotation Term="OData.LongDescription" String="This property shall indicate the allowable numeric values, inclusive ranges of values, and incremental step values for this parameter as applied to this action target, as defined in the 'Allowable values for numbers and durations' clause of the Redfish Specification. For arrays, this property shall represent the allowable values for each array member. This property shall only be present for numeric parameters or string parameters that specify a duration."/>
258 <Annotation Term="OData.LongDescription" String="This property shall contain a regular expression that describes the allowable values for this parameter as applied to this action target. For arrays, this property shall represent the allowable values for each array member. This property shall only be present for string parameters."/>
285 <Annotation Term="OData.LongDescription" String="This property shall contain the descriptions of allowable values for this parameter. The descriptions shall appear in the same array order as the `AllowableValues` property. For arrays, this property shall represent the descriptions of allowable values for each array member."/>
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-numa.rst | 98 distance attributes for the same associativity arrays, as the following
249 The spapr implementation does not support multiple associativity arrays per
264 All the associativity arrays are initialized with NUMA id in all associativity
290 Doing the same to node 2 and node 3, these are the associativity arrays
318 The kernel will read these arrays and will calculate the following NUMA topology for
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/ledmon/ |
| H A D | ledmon_0.97.bb | 4 utilizing MD devices (aka Linux Software RAID) for RAID arrays.\
|
| /openbmc/openbmc/poky/meta/recipes-support/popt/ |
| H A D | popt_1.19.bb | 2 … more powerful argument expansion. Popt can parse arbitrary argv[] style arrays and automatically …
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/uthash/ |
| H A D | uthash_2.3.0.bb | 5 * utarray.h implements dynamic arrays using macros\n\
|
| /openbmc/openbmc/poky/meta/recipes-support/libcap/files/ |
| H A D | 0001-nativesdk-libcap-Raise-the-size-of-arrays-containing.patch | 4 Subject: [PATCH] nativesdk-libcap: Raise the size of arrays containing dl
|
| /openbmc/bmcweb/scripts/ |
| H A D | generate_schema_enums.py | 110 # nlohmann::json apparently uses c style arrays in their enum
112 # the C arrays are in their code not bmcwebs, so we have to explicitly
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/fbida/files/ |
| H A D | support-jpeg-turbo.patch | 77 * coefficient arrays and thus do not require any lossy decompression
86 * arrays for most of the transforms. That could result in much thrashing
89 + * If cropping or trimming is involved, the destination arrays may be smaller
90 + * than the source arrays. Note it is not possible to do horizontal flip
98 * 1. Both the source and destination virtual arrays are allocated from the
895 * We allocate the workspace virtual arrays from the source decompression
896 * object, so that all the arrays (both the original data and the workspace)
900 * the source's virtual arrays).
1048 + /* Figure out whether we need workspace arrays,
1069 - /* Need workspace arrays having same dimensions as source image.
[all …]
|