0ee1456ab2
Updating to the latest korg -stable release that comprises
the following commits:
7217df812798 Linux 5.15.60
5c5c77746ce1 x86/speculation: Add LFENCE to RSB fill sequence
7fcd99e889c0 x86/speculation: Add RSB VM Exit protections
c81d1bb58c88 macintosh/adb: fix oob read in do_adb_query() function
d98cf2b40c20 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
ee421ad8973b Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
59689a843bc9 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
b653eeaa8cf8 Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
d4f921efb4bf Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
04e3388eeb47 Bluetooth: btusb: Add support of IMC Networks PID 0x3568
6a5ec48fb752 dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
88e088e29487 Bluetooth: hci_bcm: Add DT compatible for CYW55572
2aa38f0af306 Bluetooth: hci_bcm: Add BCM4349B1 variant
37b385c78cd5 btrfs: zoned: fix critical section of relocation inode writeback
5e04c8bf42d8 btrfs: zoned: prevent allocation from previous data relocation BG
775871d4be0d arm64: set UXN on swapper page tables
a619a0312099 KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
e423893fe320 selftests: KVM: Handle compiler optimizations in ucall
bc2cee443c74 tools/kvm_stat: fix display of error when multiple processes are found
9acd899d2feb KVM: selftests: Make hyperv_clock selftest more stable
ad6fd99d5feb KVM: x86: do not set st->preempted when going back to user space
92343314d34e KVM: x86: do not report a vCPU as preempted outside instruction boundaries
3d4c28475ee3 crypto: arm64/poly1305 - fix a read out-of-bound
397c2116cbe2 ACPI: APEI: Better fix to avoid spamming the console with old error logs
e7170bcda613 ACPI: video: Shortening quirk list by identifying Clevo by board_name only
3a5fab5c4505 ACPI: video: Force backlight native for some TongFang devices
9894717519cc tools/vm/slabinfo: Handle files in debugfs
7ad47f414b40 block: fix default IO priority handling again
e889a4c440eb selftests/bpf: Check dst_port only on the client socket
119debdb9f25 selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
df9692b8a319 x86/speculation: Make all RETbleed mitigations 64-bit only
(From OE-Core rev: 9d8d44dc6cc882d45004711cebe6f47f0bba4ffd)
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>
(cherry picked from commit 04d334d8881921a1a20407bc8428c7b9c9c80d2d)
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.