88457f1a23
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
3330a8d33e08 Linux 5.15.201
cfd5eadd051a USB: serial: option: add Telit FN920C04 RNDIS compositions
438a405fbad6 f2fs: fix out-of-bounds access in sysfs attribute read/write
2f67ff1e15a8 f2fs: fix to avoid UAF in f2fs_write_end_io()
6167af934f95 fbdev: smscufx: properly copy ioctl memory to kernelspace
52916878db2b fbdev: rivafb: fix divide error in nv3_arb()
fa9fb38f5fe9 PCI: endpoint: Avoid creating sub-groups asynchronously
7036aff5a5e8 PCI: endpoint: Remove unused field in struct pci_epf_group
8055827352b7 PCI: endpoint: Automatically create a function specific attributes group
b74408de1f22 scsi: qla2xxx: Free sp in error path to fix system crash
794563147038 scsi: qla2xxx: Reduce fabric scan duplicate code
23507a811081 scsi: qla2xxx: Remove dead code (GNN ID)
da9939b1ed8b scsi: qla2xxx: Use named initializers for port_[d]state_str
f2bbb4db0e4a scsi: qla2xxx: Fix bsg_done() causing double free
c71dfb7833db bus: fsl-mc: fix use-after-free in driver_override_show()
38770e103e4e bus: fsl-mc: Replace snprintf and sprintf with sysfs_emit in sysfs show functions
6dd2645cf080 smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()
dc5f09466448 crypto: virtio - Remove duplicated virtqueue_kick in virtio_crypto_skcipher_crypt_req
338d40bab283 mptcp: fix race in mptcp_pm_nl_flush_addrs_doit()
ec7b6a042414 selftests: mptcp: pm: ensure unknown flags are ignored
51df5513cca6 net: dsa: free routing table on probe failure
4a6e4c56721a smb: client: set correct id, uid and cruid for multiuser automounts
b0bb67385480 btrfs: fix racy bitfield write in btrfs_clear_space_info_full()
cfdb22762f90 Revert "wireguard: device: enable threaded NAPI"
20c83788eafe gpiolib: acpi: Fix gpio count with string references
612ffe1f4f04 ASoC: fsl_xcvr: fix missing lock in fsl_xcvr_mode_put()
ff96318c22fa platform/x86: panasonic-laptop: Fix sysfs group leak in error path
af673209d43b platform/x86: classmate-laptop: Add missing NULL pointer checks
72f97ee4950d drm/tegra: hdmi: sor: Fix error: variable ‘j’ set but not used
f2521ab1f63a romfs: check sb_set_blocksize() return value
f14e997a372a gpio: sprd: Change sprd_gpio lock to raw_spin_lock
1fe2603fb171 ALSA: hda/realtek: Fix headset mic for TongFang X6AR55xU
86588916e188 gpio: omap: do not register driver in probe()
7e0b2cdbe660 scsi: qla2xxx: Query FW again before proceeding with login
891f9969a29e scsi: qla2xxx: Delay module unload while fabric scan in progress
a46f81c1e627 scsi: qla2xxx: Validate sp before freeing associated memory
ba18e5f22f26 nilfs2: Fix potential block overflow that cause system hang
8ee8ccfd60bf crypto: virtio - Add spinlock protection with virtqueue notification
31aff96a41ae crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly
a60b17cedb44 crypto: octeontx - Fix length check to avoid truncation in ucode_load_store
(From OE-Core rev: 65c5b6d33aa81de3e85452a1c1e4395e49addcca)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Paul Barker <paul@pbarker.dev>
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.