492e59b331
Updating to the latest korg -stable release that comprises
the following commits:
76ba310227d2 Linux 6.1.32
cd51ba98aeaa tools headers UAPI: Sync the linux/in.h with the kernel sources
2cd02ae65654 netfilter: ctnetlink: Support offloaded conntrack entry deletion
55ce796e9b0a cpufreq: amd-pstate: Add ->fast_switch() callback
c18f6919b4e7 cpufreq: amd-pstate: Update policy->cur in amd_pstate_adjust_perf()
efc8ec1636fa block: fix bio-cache for passthru IO
5d08604754e8 Revert "thermal/drivers/mellanox: Use generic thermal_zone_get_trip() function"
2333dbc88f38 bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
6c1fad655b40 drm/amd: Don't allow s0ix on APUs older than Raven
83a7f27c5b94 octeontx2-af: Add validation for lmac type
3236221bb8e4 RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task"
592af07ac0c8 wifi: iwlwifi: mvm: fix potential memory leak
0c469078bde4 wifi: iwlwifi: mvm: support wowlan info notification version 2
b5ceb6aac607 wifi: rtw89: correct 5 MHz mask setting
07c8c1a3cfcf net: phy: mscc: enable VSC8501/2 RGMII RX clock
7c95f56995c6 page_pool: fix inconsistency for page_pool_ring_[un]lock()
7dccd5fa7edb net: page_pool: use in_softirq() instead
cd3c5e4e0d60 vfio/type1: check pfn valid before converting to struct page
6793a3c6326e blk-mq: fix race condition in active queue accounting
fe735073a50e bpf, sockmap: Incorrectly handling copied_seq
dd628fc697ee bpf, sockmap: Wake up polling after data copy
ab90b68f650e bpf, sockmap: TCP data stall on recv before accept
3a2129ebae35 bpf, sockmap: Handle fin correctly
ba4fec5bd6f8 bpf, sockmap: Improved check for empty queue
1e4e379ccde8 bpf, sockmap: Reschedule is now done through backlog
9f4d7efb3345 bpf, sockmap: Convert schedule_work into delayed_work
4ae2af3e59e2 bpf, sockmap: Pass skb ownership through read_skb
49b5b5bfeef1 gpio-f7188x: fix chip name and pin count on Nuvoton chip
085f27f48c84 net/mlx5: E-switch, Devcom, sync devcom events and devcom comp register
3347ac7a8160 tls: rx: strp: preserve decryption status of skbs when needed
ba93977437e7 tls: rx: strp: factor out copying skb data
52a89de3e9f2 tls: rx: strp: force mixed decrypted records into copy mode
c48b8399e430 tls: rx: strp: fix determining record length in copy mode
ecd9f6ed9ed2 tls: rx: strp: set the skb->len of detached / CoW'ed skbs
e734a693a24c tls: rx: device: fix checking decryption status
b3e54fb3a35d platform/x86/amd/pmf: Fix CnQF and auto-mode after resume
8e8c33cc89a0 selftests/bpf: Fix pkg-config call building sign-file
ca39992f1048 firmware: arm_ffa: Fix usage of partition info get count flag
3f5413c95445 ipv{4,6}/raw: fix output xfrm lookup wrt protocol
6728486447ee inet: Add IP_LOCAL_PORT_RANGE socket option
(From OE-Core rev: 34ba408ca84839e82dba63e2f6b4673e8d5caaa2)
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.