47154e9a1f
Updating to the latest korg -stable release that comprises
the following commits:
42616e0f09fb Linux 6.1.15
c87fb861ec18 USB: core: Don't hold device lock while reading the "descriptors" sysfs file
c49bd6c2dd1b scripts/tags.sh: fix incompatibility with PCRE2
a591d9fd7001 fs: use consistent setgid checks in is_sxid()
89f5f21b960e attr: use consistent sgid stripping checks
c1df288f4495 attr: add setattr_should_drop_sgid()
e44f23ef9160 fs: move should_remove_suid()
18c2750856dc attr: add in_group_or_capable()
118ad80d27d9 drm/amd/display: Properly reuse completion structure
c9d3eb6151b3 usb: typec: pd: Remove usb_suspend_supported sysfs from sink PDO
fb9a79557942 arm64: dts: uniphier: Fix property name in PXs3 USB node
ec357cd3e8af usb: gadget: u_serial: Add null pointer check in gserial_resume
ad5914431b70 USB: serial: option: add support for VW/Skoda "Carstick LTE"
d9651c258d66 usb: dwc3: pci: add support for the Intel Meteor Lake-M
075e2099c32c drm/amd/display: Fix race condition in DPIA AUX transfer
4da108082a32 drm/amd/display: Move DCN314 DOMAIN power control to DMCUB
a595a81df673 vc_screen: don't clobber return value in vcs_read
ea4c208efea4 net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues().
d879a777d148 bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state
f2173508b195 PM: sleep: Avoid using pr_cont() in the tasks freezing code
0c2f28f01fce x86/cpu: Add Lunar Lake M
bcc844436312 selftests: ocelot: tc_flower_chains: make test_vlan_ingress_modify() more comprehensive
56b6ea55f1dc HID: Ignore battery for ELAN touchscreen 29DF on HP
a03cc84f70a0 ASoC: codecs: es8326: Fix DTS properties reading
0412fe1deab1 HID: core: Fix deadloop in hid_apply_multiplier.
b7641733a4a1 neigh: make sure used and confirmed times are valid
6595071a3604 ARM: dts: stihxxx-b2120: fix polarity of reset line of tsin0 port
39cdf021fa05 ASoC: SOF: amd: Fix for handling spurious interrupts from DSP
8988889aaeb5 powerpc: Don't select ARCH_WANTS_NO_INSTR
ce77f44cb9ad IB/hfi1: Assign npages earlier
d06e776698ad ASoC: rt715-sdca: fix clock stop prepare timeout issue
46abcdf96db2 arm64: dts: rockchip: align rk3399 DMC OPP table with bindings
07c5877e1444 btrfs: send: limit number of clones and allocated memory size
91210aca68f3 pinctrl: amd: Fix debug output for debounce time
fdbcacfe495d ACPI: NFIT: fix a potential deadlock during NFIT teardown
1b7730f20355 HID: Ignore battery for Elan touchscreen on Asus TP420IA
0773ecf7bcda HID: elecom: add support for TrackBall 056E:011C
860a9c0509db arm64: dts: rockchip: fix probe of analog sound card on rock-3a
6a63f9795f6e arm64: dts: rockchip: add missing #interrupt-cells to rk356x pcie2x1
59770f4b5237 ARM: dts: rockchip: add power-domains property to dp node on rk3288
69eca8dd3c61 arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc
fd606d611560 arm64: dts: rockchip: reduce thermal limits on rk3399-pinephone-pro
0b892d8fe90b Fix XFRM-I support for nested ESP tunnels
(From OE-Core rev: 4ed1c0990a897f8e6bf916de5d75a09b2c9106c9)
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.