09a1f63b51
Updating to the latest korg -stable release that comprises
the following commits:
0f4ac6b4c5f0 Linux 6.1.37
323846590c55 xtensa: fix NOMMU build with lock_mm_and_find_vma() conversion
c2d89256de75 csky: fix up lock_mm_and_find_vma() conversion
4a1db15878aa parisc: fix expand_stack() conversion
0a1da2dde461 sparc32: fix lock_mm_and_find_vma() conversion
00f04a3385f7 Revert "thermal/drivers/mediatek: Use devm_of_iomap to avoid resource leak in mtk_thermal_probe"
a536383ef030 HID: logitech-hidpp: add HIDPP_QUIRK_DELAYED_INIT for the T651.
d89750b19681 HID: wacom: Use ktime_t rather than int when dealing with timestamps
879e79c3aead HID: hidraw: fix data race on device refcount
cae854249578 fbdev: fix potential OOB read in fast_imageblit()
e6bbad75712a mm: always expand the stack with the mmap write lock held
c4b31d1b694e execve: expand new process stack manually ahead of time
6a6b5616c3d0 mm: make find_extend_vma() fail if write lock not held
48c232819e77 powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma()
21ee33d51bf9 mm/fault: convert remaining simple cases to lock_mm_and_find_vma()
1f4197f050de arm/mm: Convert to using lock_mm_and_find_vma()
ac764deea709 riscv/mm: Convert to using lock_mm_and_find_vma()
7227d70acc78 mips/mm: Convert to using lock_mm_and_find_vma()
82972ea17b47 powerpc/mm: Convert to using lock_mm_and_find_vma()
b92cd80e5f0b arm64/mm: Convert to using lock_mm_and_find_vma()
755aa1bc6aaf mm: make the page fault mmap locking killable
d6a5c7a1a6e5 mm: introduce new 'lock_mm_and_find_vma()' page fault helper
4e2ad53ababe maple_tree: fix potential out-of-bounds access in mas_wr_end_piv()
31cde3bdadca can: isotp: isotp_sendmsg(): fix return error fix on TX path
0af4750eaaed x86/smp: Cure kexec() vs. mwait_play_dead() breakage
6d3b2e0aef6c x86/smp: Use dedicated cache-line for mwait_play_dead()
50a1abc67702 x86/smp: Remove pointless wmb()s from native_stop_other_cpus()
e47037d28b73 x86/smp: Dont access non-existing CPUID leaf
edadebb349e8 x86/smp: Make stop_other_cpus() more robust
94a69d699941 x86/microcode/AMD: Load late on both threads too
84f077802e56 mm, hwpoison: when copy-on-write hits poison, take page offline
4af5960d7cd4 mm, hwpoison: try to recover from copy-on write faults
69925a346acb mptcp: ensure listener is unhashed before updating the sk status
42a018a796d1 mm/mmap: Fix error return in do_vmi_align_munmap()
a149174ff8bb mm/mmap: Fix error path in do_vmi_align_munmap()
(From OE-Core rev: 4d43c9ebcb0308d9178f6f44c02cac13de126c92)
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.