0bff47afa0
Updating linux-yocto/5.15 to the latest korg -stable release that comprises the following commits: 57dcae4a8b93 Linux 5.15.10 dbcda209899a perf inject: Fix itrace space allowed for new attributes 5b4a8fbe4b0b fuse: make sure reclaim doesn't write the inode 18fc0ba9b10e staging: most: dim2: use device release method 9985d29c4755 tracing: Fix a kmemleak false positive in tracing_map 43b145f3a20a drm/amdkfd: process_info lock not needed for svm c21cff0ea6b2 drm/amd/display: add connector type check for CRC source set d9e63f180fc8 drm/amdkfd: fix double free mem structure 00a3f7fb7ae3 drm/amd/display: Fix for the no Audio bug with Tiled Displays 62477b3a86d6 drm/amdgpu: check atomic flag to differeniate with legacy path 796ddc81437b drm/amdgpu: cancel the correct hrtimer on exit 4c986072a8c9 net: netlink: af_netlink: Prevent empty skb by adding a check on len. 2d5ba2f40e73 i2c: rk3x: Handle a spurious start completion interrupt flag a5a0cc7c7b84 parisc/agp: Annotate parisc agp init functions with __init f66f84309623 ALSA: hda/hdmi: fix HDA codec entry table order for ADL-P 5eceb6a60a53 ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid ced9b762f2d6 loop: Use pr_warn_once() for loop_control_remove() warning 095a04e0b320 net/mlx4_en: Update reported link modes for 1/10G 8605743472c5 Revert "tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP" 0700eab4df5b s390/test_unwind: use raw opcode instead of invalid instruction 2b12c89527ae KVM: arm64: Save PSTATE early on exit 906f7797a38f drm/msm/dp: Avoid unpowered AUX xfers that caused crashes dc6c1eddfc74 drm/msm/dsi: set default num_data_lanes d2db21103d84 drm/msm/a6xx: Fix uinitialized use of gpu_scid f6db3d98f876 drm/msm: Fix null ptr access msm_ioctl_gem_submit() 9cbb957441ed i2c: virtio: fix completion handling 304aa6a73189 vmxnet3: fix minimum vectors alloc issue 569670a02e21 ice: fix FDIR init missing when reset VF 76db15314582 RDMA/irdma: Don't arm the CQ more than two times if no CE for this CQ 918e62519834 RDMA/irdma: Report correct WC errors b260dfed222b RDMA/irdma: Fix a potential memory allocation issue in 'irdma_prm_add_pble_mem()' 11eebcf63e98 RDMA/irdma: Fix a user-after-free in add_pble_prm 1ac287b7b615 netfs: Fix lockdep warning from taking sb_writers whilst holding mmap_lock cff728217a2b perf bpf_skel: Do not use typedef to avoid error on old clang 134151c3b11d clk: qcom: sm6125-gcc: Swap ops of ice and apps on sdcc1 439250c09785 dt-bindings: media: nxp,imx7-mipi-csi2: Drop bad if/then schema d17a8d12a6da inet: use #ifdef CONFIG_SOCK_RX_QUEUE_MAPPING consistently c6aa8873468c mtd: rawnand: Fix nand_choose_best_timings() on unsupported interface 0c7b48887c34 mtd: rawnand: Fix nand_erase_op delay e3bc4d4b50ca RDMA/mlx5: Fix releasing unallocated memory in dereg MR flow acb53e47db1f RDMA: Fix use-after-free in rxe_queue_cleanup c0d44c58afdd hwmon: (corsair-psu) fix plain integer used as NULL pointer d89e4211b517 nfc: fix segfault in nfc_genl_dump_devices_done 14655b6d4204 Linux 5.15.9 3be0c72f5153 netfilter: selftest: conntrack_vrf.sh: fix file permission (From OE-Core rev: 1fb12d42dd4112e8fa2ec7eeb562c115c3b49ada) 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.