Bruce Ashfield
9524eaf69d
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
56865d9b7074c Linux 6.6.126
673dafb9a8634 Revert "driver core: enforce device_lock for driver_match_device()"
ae462074fde3b Linux 6.6.125
1c04c3a4de8d4 gpio: omap: do not register driver in probe()
455e882192c98 mptcp: fix race in mptcp_pm_nl_flush_addrs_doit()
2b890bc3a5774 selftests: mptcp: pm: ensure unknown flags are ignored
8df235f768cea spi: cadence-quadspi: Implement refcount to handle unbind during busy
665e570600733 vsock/test: verify socket options after setting them
a9e757473561d netfilter: nft_set_pipapo: prevent overflow in lookup table allocation
1c4f72fa96993 netfilter: nf_tables: missing objects with no memcg accounting
30405b23b4d5e nfsd: don't ignore the return code of svc_proc_register()
57770faaff8ee net: sfp: Fix quirk for Ubiquiti U-Fiber Instant SFP module
dccf7bc011d0e scsi: qla2xxx: Query FW again before proceeding with login
aed16d37696f4 scsi: qla2xxx: Free sp in error path to fix system crash
528b2f1027edf scsi: qla2xxx: Delay module unload while fabric scan in progress
ccbfcaa4b88e5 scsi: qla2xxx: Allow recovery for tape devices
949010291bb94 scsi: qla2xxx: Validate sp before freeing associated memory
71dee092903ad wifi: rtw88: Fix alignment fault in rtw_core_enable_beacon()
df1e20796c9f3 nilfs2: Fix potential block overflow that cause system hang
dd1f6c9206385 crypto: virtio - Remove duplicated virtqueue_kick in virtio_crypto_skcipher_crypt_req
d6f0d58680868 crypto: virtio - Add spinlock protection with virtqueue notification
6edf8df4bd29f crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly
7dbeeafcb6e50 crypto: octeontx - Fix length check to avoid truncation in ucode_load_store
6dda9f0699054 Bluetooth: btusb: Add USB ID 7392:e611 for Edimax EW-7611UXB
adc1796eced46 driver core: enforce device_lock for driver_match_device()
787769c8cc504 smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()
5accdc5b7f28a ksmbd: fix infinite loop caused by next_smb2_rcv_hdr_off reset in error paths
4386f6af8aaed smb: client: split cached_fid bitfields to avoid shared-byte RMW races
(From OE-Core rev: d5ac249edb6ca794fc72cef09a27c65ffed8879c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Fabien Thomas <fabien.thomas@smile.fr>
Signed-off-by: Paul Barker <paul@pbarker.dev>
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
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
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.