cd05fa7593
Updating to the latest korg -stable release that comprises
the following commits:
4bf7f350c163 Linux 5.15.37
f59e6886cafb selftests/bpf: Add test for reg2btf_ids out of bounds access
dcecd95a1357 mm: gup: make fault_in_safe_writeable() use fixup_user_fault()
4a0123bdb064 btrfs: fallback to blocking mode when doing async dio over multiple extents
c81c4f566660 btrfs: fix deadlock due to page faults during direct IO reads and writes
640a6be8e861 gfs2: Fix mmap + page fault deadlocks for direct I/O
f86f8d27840a iov_iter: Introduce nofault flag to disable page faults
6e213bc61446 gup: Introduce FOLL_NOFAULT flag to disable page faults
d3b744791bf0 iomap: Add done_before argument to iomap_dio_rw
ea7a57858875 iomap: Support partial direct I/O on user copy failures
a00cc46f97b9 iomap: Fix iomap_dio_rw return value for user copies
81a7fc397a62 gfs2: Fix mmap + page fault deadlocks for buffered I/O
38b58498819a gfs2: Eliminate ip->i_gh
8d363d817353 gfs2: Move the inode glock locking to gfs2_file_buffered_write
416a705304e5 gfs2: Introduce flag for glock holder auto-demotion
b25cfbc0e7de gfs2: Clean up function may_grant
b88b998579ee gfs2: Add wrapper for iomap_file_buffered_write
1d91c912e7d1 iov_iter: Introduce fault_in_iov_iter_writeable
30e66b1dfcbb iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable
923f05a660e6 gup: Turn fault_in_pages_{readable,writeable} into fault_in_{readable,writeable}
19cbd78fb26a mm: kfence: fix objcgs vector allocation
10033fa72d41 ARM: dts: socfpga: change qspi to "intel,socfpga-qspi"
e8749d608847 spi: cadence-quadspi: fix write completion support
8c39925e98d4 bpf: Fix crash due to out of bounds access into reg2btf_ids.
379382b347db bpf/selftests: Test PTR_TO_RDONLY_MEM
2a77c58726ab bpf: Add MEM_RDONLY for helper args that are pointers to rdonly mem.
15166bb3000f bpf: Make per_cpu_ptr return rdonly PTR_TO_MEM.
b710f73704d6 bpf: Convert PTR_TO_MEM_OR_NULL to composable types.
b453361384c2 bpf: Introduce MEM_RDONLY flag
8d38cde47a7e bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL
3c141c82b958 bpf: Replace RET_XXX_OR_NULL with RET_XXX | PTR_MAYBE_NULL
d58a396fa6c9 bpf: Replace ARG_XXX_OR_NULL with ARG_XXX | PTR_MAYBE_NULL
a76020980b9f bpf: Introduce composable reg, ret and arg types.
e52da8e4632f floppy: disable FDRAWCMD by default
(From OE-Core rev: 786e668bdda1181438cbe570fa1155ad3b7f06d9)
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.