9ae693cd21
Updating to the latest korg -stable release that comprises
the following commits:
59b13c2b647e Linux 6.1.52
4a6284a2fc63 pinctrl: amd: Don't show `Invalid config param` errors
7bec12fa9813 usb: typec: tcpci: clear the fault status bit
4da07e958bfd nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
fdbfc54d5399 nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
689561db6869 dt-bindings: sc16is7xx: Add property to change GPIO function
dca7c9965141 tcpm: Avoid soft reset when partner does not support get_status
a1fc0096921c fsi: master-ast-cf: Add MODULE_FIRMWARE macro
b5c7bc370e03 firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
b7366429626e serial: sc16is7xx: fix bug when first setting GPIO direction
682f9b944374 serial: sc16is7xx: fix broken port 0 uart init
4b3de7d2f869 serial: qcom-geni: fix opp vote on shutdown
1cd102aaedb2 wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU
74ceef6e6925 wifi: mt76: mt7921: do not support one stream on secondary antenna only
179c65828593 Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race condition
86b818e2495d staging: rtl8712: fix race condition
bd69537c1a2c HID: wacom: remove the battery when the EKR is off
48729a1d2a7a usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
c564d4f91a0c usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
bfc4ccc0bcae ALSA: usb-audio: Fix init call orders for UAC1
69d9330f2eff USB: serial: option: add FOXCONN T99W368/T99W373 product
34f396f7abd0 USB: serial: option: add Quectel EM05G variant (0x030e)
5d0fe30be4e2 modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
36231e2c4ebd rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
915219699da1 net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
4dab89cccd8c mmc: au1xmmc: force non-modular build and remove symbol_get usage
ac6fa0e04be0 ARM: pxa: remove use of symbol_get()
cf859267e639 ksmbd: reduce descriptor size if remaining bytes is less than request size
d070c4dd2a5b ksmbd: replace one-element array with flex-array member in struct smb2_ea_info
30fd6521b2fb ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob()
7d8855fd849d ksmbd: fix wrong DataOffset validation of create context
1ce9ebc96eda erofs: ensure that the post-EOF tails are all zeroed
(From OE-Core rev: 3dc84243cfb11df1e483568093b2214d15f99e5d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 9be500bb695d0c6f863397d2f4b17d505427001a)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
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.