5eddd6cd2e
Updating to the latest korg -stable release that comprises
the following commits:
0fe4548663f7 Linux 5.10.162
189556b05e17 io_uring: pass in EPOLL_URING_WAKE for eventfd signaling and wakeups
4ef66581d7fd eventfd: provide a eventfd_signal_mask() helper
2f093775022b eventpoll: add EPOLL_URING_WAKE poll wakeup flag
b76c5373f084 Revert "proc: don't allow async path resolution of /proc/self components"
87cb08dc6b4f Revert "proc: don't allow async path resolution of /proc/thread-self components"
a3025359ffa7 net: remove cmsg restriction from io_uring based send/recvmsg calls
6ef2b4728a00 task_work: unconditionally run task_work from get_signal()
c91ab04781f9 signal: kill JOBCTL_TASK_WORK
788d0824269b io_uring: import 5.15-stable io_uring
ed3005032993 task_work: add helper for more targeted task_work canceling
831cb78a2a5e kernel: don't call do_exit() for PF_IO_WORKER threads
9ded44b69c71 kernel: stop masking signals in create_io_thread()
f0a5f0dc0131 x86/process: setup io_threads more like normal user space threads
dd26e2cec74f arch: ensure parisc/powerpc handle PF_IO_WORKER in copy_thread()
320c8057eceb arch: setup PF_IO_WORKER threads like PF_KTHREAD
000de389ad7b entry/kvm: Exit to user mode when TIF_NOTIFY_SIGNAL is set
0f735cf52bd0 kernel: allow fork with TIF_NOTIFY_SIGNAL pending
4b4d2c79921a coredump: Limit what can interrupt coredumps
90a2c3821bbf kernel: remove checking for TIF_NOTIFY_SIGNAL
61bdeb142e8f task_work: remove legacy TWA_SIGNAL path
6e2bce21acb4 alpha: fix TIF_NOTIFY_SIGNAL handling
db911277a2b3 ARC: unbork 5.11 bootup: fix snafu in _TIF_NOTIFY_SIGNAL handling
a1240cc413eb ia64: don't call handle_signal() unless there's actually a signal queued
e1402ba4df20 sparc: add support for TIF_NOTIFY_SIGNAL
78a53ff02656 riscv: add support for TIF_NOTIFY_SIGNAL
57e833a0a03d nds32: add support for TIF_NOTIFY_SIGNAL
751fedb9ba5d ia64: add support for TIF_NOTIFY_SIGNAL
48e9e35d33d6 h8300: add support for TIF_NOTIFY_SIGNAL
c82617d9decc c6x: add support for TIF_NOTIFY_SIGNAL
30b78a17ac8f alpha: add support for TIF_NOTIFY_SIGNAL
bf0b619593cd xtensa: add support for TIF_NOTIFY_SIGNAL
1bee9dbbcabb arm: add support for TIF_NOTIFY_SIGNAL
02d383a59cbf microblaze: add support for TIF_NOTIFY_SIGNAL
19f3e328b4c6 hexagon: add support for TIF_NOTIFY_SIGNAL
c2037d61dec2 csky: add support for TIF_NOTIFY_SIGNAL
12284aec880f openrisc: add support for TIF_NOTIFY_SIGNAL
3fde31e96262 sh: add support for TIF_NOTIFY_SIGNAL
dc808ffd9778 um: add support for TIF_NOTIFY_SIGNAL
0aef2ec06394 s390: add support for TIF_NOTIFY_SIGNAL
8ca2e5709922 mips: add support for TIF_NOTIFY_SIGNAL
abab3d4444b5 powerpc: add support for TIF_NOTIFY_SIGNAL
45b365bc6c1b parisc: add support for TIF_NOTIFY_SIGNAL
cf3c64867319 nios32: add support for TIF_NOTIFY_SIGNAL
fe137f46d41f m68k: add support for TIF_NOTIFY_SIGNAL
79a9991e87fe arm64: add support for TIF_NOTIFY_SIGNAL
2dbb0354517b arc: add support for TIF_NOTIFY_SIGNAL
4b1dcf8ec9b2 x86: Wire up TIF_NOTIFY_SIGNAL
eb42e7b30431 task_work: Use TIF_NOTIFY_SIGNAL if available
3c295bd2ddae entry: Add support for TIF_NOTIFY_SIGNAL
d2136fc145be fs: provide locked helper variant of close_fd_get_file()
57b20530363d file: Rename __close_fd_get_file close_fd_get_file
214f80e25176 fs: make do_renameat2() take struct filename
52cfde6bbf64 signal: Add task_sigpending() helper
ad0b0137953a net: add accept helper not installing fd
069ac28d9243 net: provide __sys_shutdown_sock() that takes a socket
0b8cd5d814cb tools headers UAPI: Sync openat2.h with the kernel sources
5683caa7350f fs: expose LOOKUP_CACHED through openat2() RESOLVE_CACHED
0cf0ce8fb5b1 Make sure nd->path.mnt and nd->path.dentry are always valid pointers
146fe79fff13 fix handling of nd->depth on LOOKUP_CACHED failures in try_to_unlazy*
c1fe7bd3e1aa fs: add support for LOOKUP_CACHED
36ec31201a3d saner calling conventions for unlazy_child()
e86db87191d8 iov_iter: add helper to save iov_iter state
1500fed00878 kernel: provide create_io_thread() helper
1a9148dfd8e0 Linux 5.10.161
eec1c3ade48b net: loopback: use NET_NAME_PREDICTABLE for name_assign_type
f3fe6817156a Bluetooth: L2CAP: Fix u8 overflow
7c3a523c9b19 HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk
1d5db0c322ae HID: ite: Enable QUIRK_TOUCHPAD_ON_OFF_REPORT on Acer Aspire Switch V 10
263a1782a618 HID: ite: Enable QUIRK_TOUCHPAD_ON_OFF_REPORT on Acer Aspire Switch 10E
a20b5eec0742 HID: ite: Add support for Acer S1002 keyboard-dock
f2479c3daaab igb: Initialize mailbox message for VF reset
9ff7aff40ef5 xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N
c8bf31a00f4f USB: serial: f81534: fix division by zero on line-speed change
5b75a0041674 USB: serial: f81232: fix division by zero on line-speed change
9895ce5ea283 USB: serial: cp210x: add Kamstrup RF sniffer PIDs
398215f78338 USB: serial: option: add Quectel EM05-G modem
c79538f32df1 usb: gadget: uvc: Prevent buffer overflow in setup handler
8b2f86f82c0e udf: Fix extending file within last block
db873b770d8a udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size
1a075f4a5494 udf: Fix preallocation discarding at indirect extent boundary
1f7f7365aee8 udf: Discard preallocation before extending file with a hole
(From OE-Core rev: d462705cd1053f841e5d06586384f7440f9ceb47)
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.