22b7454722
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
63dcc388662c Linux 5.15.16
ce2e7b97e588 mtd: fixup CFI on ixp4xx
9dada19e1096 ALSA: hda/realtek: Re-order quirk entries for Lenovo
4942295ec2af ALSA: hda/realtek: Add quirk for Legion Y9000X 2020
f76d5f9391a5 ALSA: hda/tegra: Fix Tegra194 HDA reset failure
7c452ca7bc7b ALSA: hda: ALC287: Add Lenovo IdeaPad Slim 9i 14ITL5 speaker quirk
8b046b2a63c6 ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after reboot from Windows
5b57c0efec9a ALSA: hda/realtek: Use ALC285_FIXUP_HP_GPIO_LED on another HP laptop
c104edbb5a3f ALSA: hda/realtek: Add speaker fixup for some Yoga 15ITL5 devices
3a1e48069798 KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
adf791cf905a perf annotate: Avoid TUI crash when navigating in the annotation of recursive functions
8840daa2f629 firmware: qemu_fw_cfg: fix kobject leak in probe error path
db3337ba6e4a firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
bb08a4d10164 firmware: qemu_fw_cfg: fix sysfs information leak
898e91c32d04 rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with interrupts enabled
c671cb0b0087 media: uvcvideo: fix division by zero at stream start
e2ece45f9450 video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
7760404e8487 9p: only copy valid iattrs in 9P2000.L setattr implementation
c2e7561ba7a8 remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP
252435941c33 KVM: s390: Clarify SIGP orders versus STOP/RESTART
6e8b6dcec07c KVM: x86: don't print when fail to read/write pv eoi memory
19f2dfb1a1f6 KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest
07667f43f8a8 KVM: x86: Register perf callbacks after calling vendor's hardware_setup()
18c16cef8179 perf: Protect perf_guest_cbs with RCU
e192ccc17ecf vfs: fs_context: fix up param length parsing in legacy_parse_param
c78c39a91dd4 remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided
b07490067dbc orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
ce258c74f8d9 drm/amd/display: explicitly set is_dsc_supported to false before use
d5df26479c82 devtmpfs regression fix: reconfigure on each mount
(From OE-Core rev: 64d6ad75dd0eecd4b976d821cae8119fdd903c41)
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.