95246b3291
Updating to the latest korg -stable release that comprises
the following commits:
9fd42770b507 Linux 5.10.172
da24142b1ef9 io_uring: ensure that io_init_req() passes in the right issue_flags
a25aa776b0c4 Linux 5.10.171
08681391b84d io_uring: add missing lock in io_get_file_fixed
218925bfd5d1 USB: core: Don't hold device lock while reading the "descriptors" sysfs file
c5360eec648b usb: gadget: u_serial: Add null pointer check in gserial_resume
cebcd4300af9 USB: serial: option: add support for VW/Skoda "Carstick LTE"
87c647def389 drm/virtio: Correct drm_gem_shmem_get_sg_table() error handling
0a4181b23acf drm/virtio: Fix NULL vs IS_ERR checking in virtio_gpu_object_shmem_init
a401ef0557da scripts/tags.sh: fix incompatibility with PCRE2
65c07e15f2ce scripts/tags.sh: Invoke 'realpath' via 'xargs'
1c44109c3094 md: Flush workqueue md_rdev_misc_wq in md_alloc()
80653a6e6e28 vc_screen: don't clobber return value in vcs_read
3e4bbd1f38a8 net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues().
a2957adbf3f5 bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state
75fbe1e43505 HID: core: Fix deadloop in hid_apply_multiplier.
2fd5059f4fdf neigh: make sure used and confirmed times are valid
065f6a663392 IB/hfi1: Assign npages earlier
6195cea4c738 btrfs: send: limit number of clones and allocated memory size
8e833fe47f45 ACPI: NFIT: fix a potential deadlock during NFIT teardown
abbf52efadeb ARM: dts: rockchip: add power-domains property to dp node on rk3288
1f3a209b2f4e arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc
887975834dea Fix XFRM-I support for nested ESP tunnels
(From OE-Core rev: 2f13f3e02efb83e9d935efac71bbf0b750420d23)
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.