Yi Zhao
74110869a8
ChangeLog: Version 2.03.31 - 27th February 2025 ==================================== Reduce 'mandoc -T lint' reported issues for man pages. Restore support for LVM_SUPPRESS_FD_WARNINGS (2.03.24). Fix uncache and split cache restoring original state of volume. Extend use of lockopt skip to more scenarios. Enhance error path resolving in polling code. Disallow shared activation of LV with CoW snapshot. Fix lvmlockd use in lvremove of CoW snapshot, VDO pool, and uncache. Improve mirror split with opened temporary volumes. Improve pvmove finish with opened temporary volumes. Fix backup limit for devices file, handle over 10,000 files. Ignore reported optimal_io_size not divisible by 4096. Fix busy-loop in config reading when read returned 0. Fix DM cache preserving logic (2.03.28). Improve use of lvmlockd for usecases involving thin volumes and pools. Signed-off-by: Yi Zhao <yi.zhao@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.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' 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