bc08748b3b
Updating to the latest korg -stable release that comprises
the following commits:
38ca69782268 Linux 6.4.9
2692b1574ad9 x86: fix backwards merge of GDS/SRSO bit
cf482893f721 xen/netback: Fix buffer overrun triggered by unusual packet
9b73a2a43f4d x86/srso: Tie SBPB bit setting to microcode patch detection
4974bd4b1385 x86/srso: Add a forgotten NOENDBR annotation
b155f54a92b0 x86/srso: Fix return thunks in generated code
b31eb84b6756 x86/srso: Add IBPB on VMEXIT
948e43310c20 x86/srso: Add IBPB
bf46b6249f26 x86/srso: Add SRSO_NO support
dc399c66209b x86/srso: Add IBPB_BRTYPE support
acdc883eb61e x86/srso: Add a Speculative RAS Overflow mitigation
d351cc7c14a6 x86/bugs: Increase the x86 bugs vector size to two u32s
7be4a6b1128c Documentation/x86: Fix backwards on/off logic about YMM support
2f94fb4a4231 x86/xen: Fix secondary processors' FPU initialization
6a592d977a0d x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build
6f29afbba8fc KVM: Add GDS_NO support to KVM
4da542e6b2bb x86/speculation: Add Kconfig option for GDS
c73393948612 x86/speculation: Add force option to GDS mitigation
ff0642207e24 x86/speculation: Add Gather Data Sampling mitigation
71c140aa6327 x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
7e56c238ff4a x86/fpu: Mark init functions __init
6c69f14c3e67 x86/fpu: Remove cpuinfo argument from init functions
121887418638 x86/init: Initialize signal frame size late
03e244a37a41 init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
5dc85ed21b9c init: Invoke arch_cpu_finalize_init() earlier
f9a4f2ba337c init: Remove check_bugs() leftovers
50455d685b65 um/cpu: Switch to arch_cpu_finalize_init()
4b61f3683da0 sparc/cpu: Switch to arch_cpu_finalize_init()
65b2da915cf9 sh/cpu: Switch to arch_cpu_finalize_init()
09afafc754b3 mips/cpu: Switch to arch_cpu_finalize_init()
626fefa0ba15 m68k/cpu: Switch to arch_cpu_finalize_init()
3868a6a35c95 loongarch/cpu: Switch to arch_cpu_finalize_init()
2156182d8f66 ia64/cpu: Switch to arch_cpu_finalize_init()
81da5576db4e ARM: cpu: Switch to arch_cpu_finalize_init()
f2aef93c0bc7 x86/cpu: Switch to arch_cpu_finalize_init()
e5b3acb81bd2 init: Provide arch_cpu_finalize_init()
(From OE-Core rev: 5bed09b127c977214f66ebaf63f2bdc1e1d4bde5)
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.