6ca6ee0dac
Updating to the latest korg -stable release that comprises
the following commits:
d654f7e29909 Linux 5.19.1
f6664a403f11 x86/speculation: Add LFENCE to RSB fill sequence
f826d0412d80 x86/speculation: Add RSB VM Exit protections
224b653547fa macintosh/adb: fix oob read in do_adb_query() function
7f64bc0c090c Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
651880ed7d39 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
7562b32d7531 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
17da5b394ba4 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
9122622a9d2a Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
cb79e61c28b9 Bluetooth: btusb: Add support of IMC Networks PID 0x3568
34464228344c dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
18b04e68252f Bluetooth: hci_bcm: Add DT compatible for CYW55572
f7b229ecf21a Bluetooth: hci_bcm: Add BCM4349B1 variant
60ef27c1c77f Bluetooth: hci_qca: Return wakeup for qca_wakeup
9283e708a9b8 arm64: set UXN on swapper page tables
231276d2c6cc ata: sata_mv: Fixes expected number of resources now IRQs are gone
d069dcffef84 crypto: arm64/poly1305 - fix a read out-of-bound
cd5a88272762 ACPI: APEI: Better fix to avoid spamming the console with old error logs
eb5595ac6aee ACPI: video: Shortening quirk list by identifying Clevo by board_name only
5ab9b078c4ff ACPI: video: Force backlight native for some TongFang devices
7c8e33cc2a49 tools/vm/slabinfo: Handle files in debugfs
28a9cbc1c927 block: fix default IO priority handling again
(From OE-Core rev: f1cb26e429c7be2b9ae46a0d67e6cb74aa0ce1fe)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@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.