| /openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
| H A D | read-edid | 5 * offer support for this software as long as I am capable of doing so,
10 * brief message on what you're doing. Nothing will be rejected, this is
|
| H A D | GPL-2.0-with-lmbench-restriction | 27 Without exception, they were doing so to show a skewed view of whatever
45 We're not swayed by that, our position is that we are doing the right
52 sorry if I'm a pain in the ass on this topic, but I'm doing the right
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | fuse-allow-other.out | 25 Doing operations as nobody:
53 Doing operations as nobody:
80 Doing operations as nobody:
|
| /openbmc/qemu/hw/usb/ |
| H A D | chipidea.c | 40 * Our device would not work correctly if the guest was doing
61 * but there doesn't seem to be much point in doing so, since in chipidea_dc_read()
81 * Our device would not work correctly if the guest was doing
|
| /openbmc/qemu/tests/tcg/multiarch/gdbstub/ |
| H A D | interrupt.py | 28 # Ideally, there should be no difference between what we're doing here and
32 # instructions that may have problems with what we're doing here. We don't
|
| /openbmc/openbmc/poky/meta/recipes-devtools/apt/apt/ |
| H A D | 0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch | 33 - is way more correct than reaching 100% while still doing stuff even if
34 - doing it this way is slightly bending the rules */
|
| /openbmc/openbmc/poky/meta/recipes-core/dbus/dbus-glib/ |
| H A D | test-install-makefile.patch | 38 ## build even when not doing "make check"
52 ## build even when not doing "make check"
|
| /openbmc/bmcweb/docs/ |
| H A D | HEADERS.md | 36 <https://gerrit.openbmc.org/c/openbmc/bmcweb/+/37445> Doing this exposed a
47 required for most usages. About half of the bmcweb build time is spent doing
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | App-s2p | 5 way you wish, provided you do not restrict others from doing the same.
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 216.out | 8 --- Doing COR ---
|
| H A D | 310.out | 8 --- Doing COR ---
|
| /openbmc/u-boot/include/linux/ |
| H A D | stringify.h | 4 /* Indirect stringification. Doing two levels allows the parameter to be a
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-aiodns_3.4.0.bb | 2 DESCRIPTION = "aiodns provides a simple way for doing asynchronous DNS resolutions using pycares."
|
| H A D | python3-dirty-equals_0.9.0.bb | 1 SUMMARY = "Doing dirty (but extremely useful) things with equals."
|
| /openbmc/qemu/tests/tcg/ |
| H A D | README | 2 regression testing the Tiny Code Generator doing system and user-mode
|
| /openbmc/u-boot/doc/device-tree-bindings/exynos/ |
| H A D | soc.txt | 9 property allows doing it automatically.
|
| /openbmc/u-boot/arch/x86/cpu/ |
| H A D | config.mk | 8 # DO NOT MODIFY THE FOLLOWING UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!
|
| /openbmc/phosphor-hwmon/ |
| H A D | README.iio.md | 10 device - doing this will result in undefined behavior from phosphor-hwmon-readd.
|
| /openbmc/qemu/linux-user/arm/ |
| H A D | vdso.S | 52 * While we're doing that, we might as well save LR to get a free return,
81 * lest we trip up someone doing code inspection.
|
| /openbmc/qemu/python/ |
| H A D | README.rst | 10 ``setup.py``. You will generally invoke it by doing one of the following:
24 doing, the installed package always reflects the latest version in your
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-build_1.2.2.bb | 14 # Skip dependencies as we're doing a minimal build to bootstrap
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | policy-chassis-poweron | 16 echo "Host$CHASSIS_ID doing Power Policy"
|
| /openbmc/u-boot/include/ |
| H A D | thermal.h | 24 * This must be called before doing any transfers with a Thermal device.
|
| /openbmc/u-boot/board/toradex/apalis-tk1/ |
| H A D | as3722_init.c | 90 * NOTE: We do this early because doing it later seems to hose the CPU in pmic_enable_cpu_vdd()
106 * NOTE: We do this early because doing it later seems to hose the CPU in pmic_enable_cpu_vdd()
|
| /openbmc/u-boot/doc/device-tree-bindings/remoteproc/ |
| H A D | k3-system-controller.txt | 4 K3 specific SoCs have a dedicated microcontroller for doing
|