mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-09-05 17:08:02 +00:00
edb3ef57ec
10.8.2 contains a fix for CVE-2022-0571. Full release notes (https://github.com/phoronix-test-suite/phoronix-test-suite/blob/master/ChangeLog): Phoronix Test Suite 10.8.2 13 February 2022 pts-core: Arch Linux external dependency updates pts-core: Workaround/fix PHP 5.4 usage with RHEL7-based distributions pts-core: Convert compiler / multicore / single-threaded test suites into virtual test suites since their properties can be auto-determined based on OB metadata to avoid manually maintaining them pts-core: Add virtual test suites for "riscv" and "aarch64" to make it easy to show test profiles that can run successfully on RISC-V and 64-bit Arm hardware phodevi: Improved detection for components found on the Steam Deck and other hardware phodevi: Add Arm Cortex-X1C detection phodevi: CPU temperature reporting for additional SoCs such as the Raspberry Pi 400 phoromatic: Additional input sanitization and validation improvements Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe ======= This layer depends on: URI: git://github.com/openembedded/openembedded-core.git branch: master luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below pacman -S lib32-gcc-libs lib32-glibc Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject' When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"' You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI. layer maintainer: Khem Raj <raj.khem@gmail.com>