acdb1bb14e
We drop our previously backported patches for v6.8 kernels as they are
part of the 2.13.12 release of lttng and we add backports for v6.9+
kernels.
Bumping lttng-modules to version v2.13.12-7-g52eb2ee9, which comprises the following commits:
52eb2ee9 Fix: dev_base_lock removed in linux 6.9-rc1
175fe77c Fix: mm_compaction_migratepages changed in linux 6.9-rc1
303434ab Fix: ASoC add component to set_bias_level events in linux 6.9-rc1
88c4e0fe Fix: ASoC snd_doc_dapm on linux 6.9-rc1
578ab207 Fix: build kvm probe on EL 8.4+
057ad399 Fix: support ext4_journal_start on EL 8.4+
3ca21738 Fix: correct RHEL range for kmem_cache_free define
4ba4f0ec Version 2.13.12
1124749b docs: Add supported versions and fix-backport policy
c302cf1d docs: Add links to project resources
d6b75831 Fix: Correct minimum version in jbd2 SLE kernel range
9e6736d6 Fix: Handle recent SLE major version codes
5d331562 Fix: build on sles15sp4
f6800492 Compile fixes for RHEL 9.3 kernels
d988f04a Fix: ext4_discard_preallocations changed in linux 6.8.0-rc3
616c60b9 Fix: btrfs_get_extent flags and compress_type changed in linux 6.8.0-rc1
8d195927 Fix: btrfs_chunk tracepoints changed in linux 6.8.0-rc1
7e8d89d1 Fix: strlcpy removed in linux 6.8.0-rc1
f4c1678d Fix: timer_start changed in linux 6.8.0-rc1
60a1e809 Fix: sched_stat_runtime changed in linux 6.8.0-rc1
(From OE-Core rev: f8be1a87f1a7e7de714d19a6b3afe59e6f177e7d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.