7cb1e0c999
Updating to the latest korg -stable release that comprises
the following commits:
6eae1503ddf9 Linux 5.10.136
1bea03b44ea2 x86/speculation: Add LFENCE to RSB fill sequence
509c2c9fe75e x86/speculation: Add RSB VM Exit protections
e5b556a7b271 macintosh/adb: fix oob read in do_adb_query() function
75742ffc3630 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
40e2e7f1bf03 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
9c45bb363e26 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
3a292cb18132 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
1a2a2e34569c Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
e81f95d03060 Bluetooth: btusb: Add support of IMC Networks PID 0x3568
918ce738e28b Bluetooth: hci_bcm: Add DT compatible for CYW55572
033a4455d9d6 Bluetooth: hci_bcm: Add BCM4349B1 variant
50763f0ac070 selftests: KVM: Handle compiler optimizations in ucall
a56e1ccdb7bb tools/kvm_stat: fix display of error when multiple processes are found
3c77292d52b3 crypto: arm64/poly1305 - fix a read out-of-bound
e2c63e1afdb3 ACPI: APEI: Better fix to avoid spamming the console with old error logs
6ccff35588d2 ACPI: video: Shortening quirk list by identifying Clevo by board_name only
a2b472b152f9 ACPI: video: Force backlight native for some TongFang devices
a01a4e9f5dc9 tun: avoid double free in tun_free_netdev
1069087e2fb1 selftests/bpf: Check dst_port only on the client socket
042fb1c281f3 selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
78c8397132dd ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()
4f3b85233660 ath9k_htc: fix NULL pointer dereference at ath9k_htc_rxep()
45b69848a2fe x86/speculation: Make all RETbleed mitigations 64-bit only
(From OE-Core rev: 3dbf621c295be2bdf1009dd52f1a4bfe55806173)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.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.