| /openbmc/qemu/tests/tcg/i386/ |
| H A D | README | 11 to test some 16 bit addressing and 32 bit with segmentation cases.
|
| /openbmc/openbmc/meta-security/meta-integrity/recipes-security/ima-evm-utils/ima-evm-utils/ |
| H A D | 0001-Do-not-get-generation-using-ioctl-when-evm_portable-.patch | 7 generation with the ioctl since in some cases this may not be supported
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | eainode.rst | 16 and i_generation of the **one** owning inode (in cases where the EA
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/multipath-tools/files/ |
| H A D | 0001-libmultipath-always-use-glibc-basename.patch | 8 therefore provide a version for such cases
|
| /openbmc/phosphor-fan-presence/docs/control/ |
| H A D | groups.md | 35 provides performance improvements in certain cases. Optional.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-cros-ec | 41 the (Intel) processor's SLP_S0 line, in order to detect cases
64 in order to detect cases where a system failed to go into deep
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | gpio-properties.rst | 101 cases like with SPI host controllers where some chip selects may be
118 Active High. Even for the cases when _DSD() is involved (see the example
230 In those cases ACPI device identification objects, _HID, _CID, _CLS, _SUB, _HRV,
313 We may consider two different cases here, i.e. when connection ID is
332 Be aware that gpiod_get_index() in cases 1 and 2, assuming that there
|
| /openbmc/bmcweb/ |
| H A D | DEVELOPING.md | 66 to the application at compile time. For cases where the implementation is
80 of exceptions should be cases where the program can be reasonably expected to
192 Security: There may be cases where maintainers make explicit breaking changes in
193 the best interest of security; In these rare cases, the maintainers and
217 And their use cases:
|
| /openbmc/linux/Documentation/driver-api/iio/ |
| H A D | intro.rst | 15 In some cases there is considerable overlap between these and IIO.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-extended/kronosnet/ |
| H A D | kronosnet_1.24.bb | 5 designed for High Availability use cases, where redundancy, security, \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/redis-plus-plus/files/ |
| H A D | 0001-CMakeLists.txt-fix-substitution-for-static-libs.patch | 8 substitution will match both cases and trash the name for hiredis_ssl.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | btrfs.rst | 42 questions, use cases, mount options, comprehensible changelogs, features,
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | eeprom.md | 5 Some fans have EEPROMs on them. In these cases, the `eeprom` JSON stanza can be
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | cpu-cooling-api.rst | 79 access patterns and so forth) causes, in most cases, a second order
80 variation. In pathological cases this variation can be significant,
|
| /openbmc/linux/Documentation/driver-api/soundwire/ |
| H A D | error_handling.rst | 42 3. Timeouts: In a number of cases such as ChannelPrepare or
61 written in valid registers. In a number of cases the standard even mentions
|
| /openbmc/openbmc-test-automation/gui/test/server_overview/ |
| H A D | test_obmc_gui_server_overview.robot | 23 # OpenBMC @ Power Off state test cases.
94 # OpenBMC @ Power Running state test cases.
|
| /openbmc/phosphor-time-manager/ |
| H A D | README.md | 79 A summary of which cases the time can be set on BMC or HOST:
126 This results in [openbmc/openbmc#3459][1], and the related test cases are
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl/liburi-perl/ |
| H A D | 0001-Skip-TODO-test-cases-that-fail.patch | 4 Subject: [PATCH] Skip TODO test cases that fail
6 TODO cases report as "not ok" with ptest-runner
|
| /openbmc/linux/Documentation/mm/ |
| H A D | mmu_notifier.rst | 6 the page table lock. But that notification is not necessary in all cases.
10 process virtual address space). There is only 2 cases when you need to notify
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | writing-bindings.rst | 61 Typical cases and caveats
76 "unevaluatedProperties:false". In other cases, usually use
|
| /openbmc/linux/Documentation/devicetree/bindings/hwmon/ |
| H A D | ntc-thermistor.yaml | 49 the cases when either pull-up or pull-down resistance is zero.
61 ground" and "connected positive" cases.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | IPMI.interface.yaml | 43 In most cases this will be 0x20 (the BMC Generator ID).
73 In most cases this will be 0x20 (the BMC Generator ID).
|
| /openbmc/qemu/docs/system/ |
| H A D | device-emulation.rst | 34 automatically created. In most cases the BUS a device is attached to
67 there are cases where features will not be reported to the guest if
|
| /openbmc/linux/arch/m68k/fpsp040/ |
| H A D | get_op.S | 502 |input is of the special cases of inf and NaN
544 | packed cases, but we must set the FPSR condition codes properly.
554 |input is of the special cases of inf and NaN
|
| /openbmc/docs/designs/ |
| H A D | redfish-resource-supplement-for-pfr.md | 111 Below are some cases, where firmware resiliency error events logged for
127 Below are some cases, where these events can be logged.
142 Below are few cases, where these events can be logged.
|