Updating to the latest korg -stable release that comprises
the following commits:
d9b4a0c83a2d Linux 5.15.98
937c15e27a63 io_uring: ensure that io_init_req() passes in the right issue_flags
bf7123dd26a0 Linux 5.15.97
cf7f9cd50013 io_uring: add missing lock in io_get_file_fixed
77358093331e USB: core: Don't hold device lock while reading the "descriptors" sysfs file
3b24c980dc07 usb: gadget: u_serial: Add null pointer check in gserial_resume
2d72795ccde2 USB: serial: option: add support for VW/Skoda "Carstick LTE"
02190d23b731 usb: dwc3: pci: add support for the Intel Meteor Lake-M
cc09a7d5a6a1 scripts/tags.sh: fix incompatibility with PCRE2
1aee4ab2c107 scripts/tags.sh: Invoke 'realpath' via 'xargs'
06740b433d9d vc_screen: don't clobber return value in vcs_read
e7f460696340 net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues().
16d319ec18b0 bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state
6dd1de27d771 staging: mt7621-dts: change palmbus address to lower case
07f0c6f9c357 x86/cpu: Add Lunar Lake M
e1b09162f268 HID: core: Fix deadloop in hid_apply_multiplier.
f1ee47003075 neigh: make sure used and confirmed times are valid
2590058fb058 IB/hfi1: Assign npages earlier
4534ea429ed8 ASoC: rt715-sdca: fix clock stop prepare timeout issue
e430f058d90c btrfs: send: limit number of clones and allocated memory size
d454a7212e17 ACPI: NFIT: fix a potential deadlock during NFIT teardown
435e8fabd19a HID: elecom: add support for TrackBall 056E:011C
6bd2f1754393 ARM: dts: rockchip: add power-domains property to dp node on rk3288
839a9c0047a1 arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc
503e3d93cf35 Fix XFRM-I support for nested ESP tunnels
765b3a0e0a81 ionic: refactor use of ionic_rx_fill()
(From OE-Core rev: 0ed52357cdc913224a298144fe5118525de7e0e1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 4961d295599b1c3822752c42891006a49aea8ff3)
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.