fdae4cc099
Updating to the latest korg -stable release that comprises
the following commits:
ebdb69c5b054 Linux 6.1.1
1d1a710c1983 KEYS: encrypted: fix key instantiation with user-provided data
e8d16a54842d cifs: fix oops during encryption
4e453324803d usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake
9222912924fc usb: typec: ucsi: Resume in separate work
c383c7c35c7b igb: Initialize mailbox message for VF reset
52d5896ba2a4 staging: r8188eu: fix led register settings
c9cacc0ab1ea xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N
c0d91ec1a16a ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
c0815ea08548 USB: serial: f81534: fix division by zero on line-speed change
3c8b21ee1404 USB: serial: f81232: fix division by zero on line-speed change
736f626ea8b8 USB: serial: cp210x: add Kamstrup RF sniffer PIDs
0b63d587c0d2 USB: serial: option: add Quectel EM05-G modem
d1a92bb8d697 usb: gadget: uvc: Prevent buffer overflow in setup handler
2cd2e9322726 udf: Fix extending file within last block
1cd3e9297d44 udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size
12a88f572d6d udf: Fix preallocation discarding at indirect extent boundary
e6b01f6a0e77 udf: Discard preallocation before extending file with a hole
fb9b502cf911 irqchip/ls-extirq: Fix endianness detection
18301e16ea55 mips: ralink: mt7621: do not use kzalloc too early
ee11da28a62e mips: ralink: mt7621: soc queries and tests as functions
a1d9199ba485 mips: ralink: mt7621: define MT7621_SYSC_BASE with __iomem
a4997bae1b5b PCI: mt7621: Add sentinel to quirks table
76c6303530eb libbpf: Fix uninitialized warning in btf_dump_dump_type_data
96c5043a4d64 x86/vdso: Conditionally export __vdso_sgx_enter_enclave()
(From OE-Core rev: 253360891b8be1b6574f8bf237ce178b42174ee5)
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.