43e38ada0f
Add 'tag' to SRC_URI Changelog: https://github.com/stephane/libmodbus/releases/tag/v3.1.12 Changes: - Fix FD_SET overflow when socket fd >= FD_SETSIZE. - Check dest pointer not null and nb in read functions. - NULL check for src and nb < 1 validation in write functions. - modbus_reply: don't compute address for FC 0x07/0x11. - Use O_NONBLOCK instead of deprecated O_NDELAY - Explicit cast for Coverity CID 416366. - Document required buffer size of modbus_receive. - Document macros for error codes corresponding to Modbus exceptions - Fix example of modbus_rtu_set_serial_mode - Test filesystem provides symlink in autogen.sh - Sync API signatures with the documentation. - Many documentation fixes and typo corrections. - Add coverage target and helper script. Signed-off-by: Andrej Kozemcak <andrej.kozemcak@siemens.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