mirror of
https://github.com/thead-yocto-mirror/meta-openembedded
synced 2026-09-06 14:14:40 +02:00
7cd43b79c5
Changelog: ========== Fix typos lvm: Fix bd_lvm_get_supported_pe_sizes in Python on 32bit tests: Create bigger devices for XFS tests tests: Use ext instead of xfs in MountTestCase.test_mount_ro_device mpath: Memory leak fix spec: Require the same version utils from plugins mdraid: Try harder to get container UUID in bd_md_detail Add a test case for DDF arrays/containers mdraid: Do not ignore errors from bd_md_canonicalize_uuid in bd_md_examine mdraid: Try harder to get container UUID in bd_md_examine mdraid: Fix copy-paste error when checking return value tests: Wait for raid and mirrored LVs to be synced before removing tests: Make smaller images for test_lvcreate_type dm: Fix comparing DM RAID member devices UUID mdraid: Fix use after free ci: Add .lgtm.yaml config for LGTM ci: Add GitHub actions for running rpmbuilds and csmock mpath: Fix potential NULL pointer dereference Fix mismatched functions return value type Signed-off-by: Wang Mingyu <wangmy@fujitsu.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>