| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-awesomeversion_24.6.0.bb | 1 …ion package to rule them all, One version package to find them, One version package to bring them …
|
| /openbmc/openbmc/poky/meta/recipes-kernel/lttng/lttng-tools/ |
| H A D | disable-tests.patch | 9 a variety of distros. Exclude them for now to work out if this is the
10 only place we see them and give SWAT/triage a break from the stream
11 of them.
|
| /openbmc/u-boot/arch/arm/mach-tegra/tegra124/ |
| H A D | psci.c | 37 * However, this doesn't work in practice. We rather need to power them in psci_board_init()
38 * up first and park them in wfi. While they are waiting there, we can in psci_board_init()
39 * indeed program the Flow Controller to powergate them on wfi, which in psci_board_init()
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 290.out | 7 # Fill all clusters with data and then discard them
19 # Fill all clusters with data and then discard them
38 # Fill all clusters with data and then discard them
51 # Fill all clusters with data and then discard them
|
| /openbmc/u-boot/drivers/input/ |
| H A D | Kconfig | 21 input and update LEDs if the keyboard has them.
30 input and update LEDs if the keyboard has them.
39 input and update LEDs if the keyboard has them.
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/musicpd/ |
| H A D | libmpdclient_2.22.bb | 19 # is likely that nobody will ever use them, so let's not install
20 # them
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-security/optee/optee-os/ |
| H A D | 0001-compile.mk-use-CFLAGS-from-environment.patch | 7 LD etc and expect them to be used. It's ok to amend
8 to them but overwriting should not be done.
15 since mappings to remove them can be set by the distro
|
| /openbmc/openbmc-build-scripts/config/ |
| H A D | .gitlint | 99 # Ignore certain rules, you can reference them by their id or by their full name
108 # Ignore certain rules, you can reference them by their id or by their full name
121 # Ignore certain rules, you can reference them by their id or by their full name
126 # You need to explicitly enable them one-by-one by adding them to the "contrib" option
|
| /openbmc/u-boot/doc/ |
| H A D | README.ramboot-ppc85xx | 13 Two of them are described below.There is also an explanation as to where these
40 All of them define CONFIG_SYS_RAMBOOT.
41 The main difference among all of them is the way the pre-environment is getting
47 How to use them:
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/bluez5/bluez5/ |
| H A D | 0001-tests-add-a-target-for-building-tests-without-runnin.patch | 4 Subject: [PATCH] tests: add a target for building tests without running them
20 +# This allows building tests without running them
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | distrodata.py | 30 The following packages failed upstream version checks. Please fix them using UPSTREAM_CHECK_URI/UPS…
46 Expected: All entries in maintainers list should have a recipe file that matches them
106 The following recipes do not have a maintainer assigned to them. Please add an entry to meta/conf/d…
121 … Summary: Test that obtaining recipes that share includes between them returns a sane result
|
| /openbmc/qemu/contrib/plugins/ |
| H A D | lockstep.c | 129 static void report_divergance(ExecState *us, ExecState *them) in report_divergance() argument
168 them->pc, them->insn_count, in report_divergance()
199 ExecState us, them; in vcpu_tb_exec() local
223 bytes = read(socket_fd, &them, sizeof(ExecState)); in vcpu_tb_exec()
235 if (us.pc != them.pc) { in vcpu_tb_exec()
236 report_divergance(&us, &them); in vcpu_tb_exec()
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/keepalived/keepalived/ |
| H A D | 0001-configure.ac-Do-not-emit-compiler-flags-into-object-.patch | 6 They contain options which have absolute paths in them e.g. --sysroot
7 therefore do not record them and make build reproducible
|
| /openbmc/openbmc/poky/meta/recipes-devtools/flex/flex/ |
| H A D | 0001-tests-add-a-target-for-building-tests-without-runnin.patch | 4 Subject: [PATCH] tests: add a target for building tests without running them
20 +# This allows building tests without running them
|
| /openbmc/openbmc/poky/meta/recipes-devtools/meson/meson/ |
| H A D | meson-wrapper | 12 # use them as native tools. Unset them to prevent this, as all the cross-compile
|
| /openbmc/openbmc/meta-raspberrypi/recipes-graphics/userland/files/ |
| H A D | 0022-all-host_applications-remove-non-existent-projects.patch | 7 however, several of them don't exist anymore. Remove them from the list of
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/mdns/mdns/ |
| H A D | 0009-remove-unneeded-headers.patch | 6 From a quick look, these seem to not be needed and having them
7 breaks the build with mbedtls 3.x. Without them it builds fine
|
| /openbmc/openbmc/poky/meta-poky/conf/templates/default/ |
| H A D | site.conf.sample | 26 # If you wish to use certain hosts without the proxy, specify them in NO_PROXY.
28 # that may not be included on HOSTTOOLS, thus add them manually through
|
| /openbmc/u-boot/tools/patman/ |
| H A D | patman | 72 Create patches from commits in a branch, check them and email them as
129 # Process commits, produce patches files, check them, email them
156 # Check the patches, and run them through 'git am' just to be sure
|
| H A D | patman.py | 72 Create patches from commits in a branch, check them and email them as
129 # Process commits, produce patches files, check them, email them
156 # Check the patches, and run them through 'git am' just to be sure
|
| /openbmc/sdbusplus/include/sdbusplus/sdbuspp_support/ |
| H A D | server.hpp | 23 * This function will unpack a message's contents, redirect them to the
24 * function 'f', and then pack them into the response message.
79 * This function will unpack a message's contents, redirect them to the
80 * function 'f', and then pack them into the response message.
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | custom-distribution.rst | 44 and then "require" them from within your distribution configuration
57 These following variables are optional and you typically set them
130 - Unless you also intend to use them, the ``poky-tiny``, ``poky-altcfg`` and
131 ``poky-bleeding`` variants and any references to them can be removed.
|
| /openbmc/qemu/scripts/ |
| H A D | make-release | 63 # Fetch edk2 submodule's submodules, since it won't have access to them via
68 # so we don't need to add them to the tarball.
70 # has, we clone them all, to avoid running into problems where EDK2
|
| /openbmc/openbmc/meta-nuvoton/recipes-bsp/images/ |
| H A D | npcm8xx-bootloader_04.03.09.bb | 6 from deploy folder, put them to IGPS input folder, and run script."
24 # Sign keys, replace them for production
26 # Configuration files, clean them if no need
|
| /openbmc/u-boot/arch/x86/cpu/qemu/ |
| H A D | e820.c | 24 * storing ACPI tables, we need to reserve them in e820 tables, in install_e820_map()
25 * otherwise kernel will reclaim them and data will be corrupted in install_e820_map()
|