24df057854
2021-10-18 lttng-tools 2.13.1 (National Chocolate Cupcake Day)
Fix: ust: app stuck on recv message during UST comm timeout scenario
Fix: ust: UST communication can return -EAGAIN
Fix: ust: segfault on lttng start on filter bytecode copy
Fix: sessiond: previously created channel cannot be enabled
Build fix: Missing message in LTTNG_DEPRECATED invocation
Fix: notification-thread: handling event from a removed tracer event src
include: add missing "extern"
include: remove spurious spaces in condition/session-rotation.h
tests: fix header of regression/ust/getcpu-override/run-getcpu-override
fix: wrong define used for GCC version check
Fix: userspace-probe: unreported error on string copy error
Fix: userspace-probe: truncating binary path for SDT
Fix: lttng: add-trigger: don't provide a default event rule type
Fix: statements with side-effects in assert statements
Fix: lttng_trace_archive_location_serialize is called on freed memory
Fix: sessiond: ust session is inactive during ust_app_global_update
Fix: common: error query for trigger action protocol error
Fix: common: un-hide two rate policy functions
Fix: include: remove unneeded declaration of lttng_session_descriptor_get_session_name
Fix: Tests: race condition in test_ns_contexts_change
Fix: Tests: race condition in test_event_tracker
Fix: man: lttng-rotate: trace file count/size limitation does not apply
Fix: runas: less-than-zero comparison of an unsigned value
Fix: runas: supplementary groups are ignored on lttng save
Docs: lttng-event-rule(7): --exclude does not exist, use --exclude-name
sessiond: logging typo: {triger, triggger} -> trigger
Fix: lttng: free sessions in cmd_destroy
Fix: lttng: free domains and channels in get_session_stats_str
0001-Fix-Tests-race-condition-in-test_event_tracker.patch
0002-Fix-Tests-race-condition-in-test_ns_contexts_change.patch
are removed since they're included in 2.13.1
(From OE-Core rev: 9541cac079b0fa4961328f610e3df3ccf5316cea)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.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
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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.