116d8a3321
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
7cc36c3e14ae Linux 5.15.2
5dbe126056fb rsi: fix control-message timeout
7d6f8d3bab72 media: staging/intel-ipu3: css: Fix wrong size comparison imgu_css_fw_init
4787caef521c staging: r8188eu: fix memleak in rtw_wx_set_enc_ext
8f60f9f6ee24 staging: rtl8192u: fix control-message timeouts
9033490a3fef staging: r8712u: fix control-message timeout
3a66e8a661a4 comedi: vmk80xx: fix bulk and interrupt message timeouts
47b4636ebdbe comedi: vmk80xx: fix bulk-buffer overflow
06ac746d57e6 comedi: vmk80xx: fix transfer-buffer overflows
d6a727a681a3 comedi: ni_usb6501: fix NULL-deref in command paths
20cebb8b620d comedi: dt9812: fix DMA buffers on stack
e7fb722586a2 isofs: Fix out of bound access for corrupted isofs image
a65c9afe9f2f staging: rtl8712: fix use-after-free in rtl8712_dl_fw
a0041453ff9e btrfs: fix lzo_decompress_bio() kmap leakage
d5dd3b44488b kfence: default to dynamic branch instead of static keys mode
93ce7441001f kfence: always use static branches to guard kfence_alloc()
5e57d171e2e6 binder: don't detect sender/target during buffer cleanup
6e8813eadf8b binder: use cred instead of task for getsecid
3f3c31dd0f8c binder: use cred instead of task for selinux checks
ff1bd01f490b binder: use euid from cred instead of using task
ec7c20d41714 Revert "proc/wchan: use printk format instead of lookup_symbol_name()"
2e93afda0520 usb-storage: Add compatibility quirk flags for iODD 2531/2541
ad5df979295b usb: musb: Balance list entry in musb_gadget_queue
72a9bf9bb16a usb: gadget: Mark USB_FSL_QE broken on 64-bit
adb1902a1246 usb: ehci: handshake CMD_RUN instead of STS_HALT
aa8a82d6db0b Revert "x86/kvm: fix vcpu-id indexed array sizes"
26ac7dec7ff0 KVM: x86: avoid warning with -Wbitwise-instead-of-logical
(From OE-Core rev: 0fe8d5a28d1161c152bf64cd67053b8f51fc7073)
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
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.