c7c869a242
Updating to the latest korg -stable release that comprises
the following commits:
d7af3e5ba454 Linux 5.15.115
e226893c935f netfilter: ctnetlink: Support offloaded conntrack entry deletion
395d846c61c5 ipv{4,6}/raw: fix output xfrm lookup wrt protocol
1bb8a65190d4 binder: fix UAF of alloc->vma in race with munmap()
1cae0d51368e binder: add lockless binder_alloc_(set|get)_vma()
dd7aff43d005 Revert "android: binder: stop saving a pointer to the VMA"
6802c700902c Revert "binder_alloc: add missing mmap_lock calls when using the VMA"
09411f1b8672 bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
0f21b8621756 xdp: xdp_mem_allocator can be NULL in trace_mem_connect().
b6c4afcbd625 irqchip/mips-gic: Don't touch vl_map if a local interrupt is not routable
13b290f02094 page_pool: fix inconsistency for page_pool_ring_[un]lock()
3af319d51474 net: page_pool: use in_softirq() instead
1c097b9db173 xdp: Allow registering memory model without rxq reference
623d965c2dee net/mlx5e: Fix SQ wake logic in ptp napi_poll context
9085886c04d9 irqchip/mips-gic: Use raw spinlock for gic_lock
4517730b4c1e irqchip/mips-gic: Get rid of the reliance on irq_cpu_online()
5fd7c1e36b0a binder: fix UAF caused by faulty buffer cleanup
c88d21c0ae32 bonding: fix send_peer_notif overflow
7ee611fc85ad Bonding: add arp_missed_max option
5b925b48bebc net: dsa: mt7530: fix network connectivity with multiple CPU ports
5a7266feaa6d net: dsa: mt7530: split-off common parts from mt7531_setup
0753c1ef2419 net: dsa: mt7530: rework mt753[01]_setup
9902f91cf666 net: dsa: introduce helpers for iterating through ports using dp
d84b42b72526 net: phy: mscc: enable VSC8501/2 RGMII RX clock
3dce2f3d8359 platform/x86: ISST: Remove 8 socket limit
017a634f9f38 platform/x86: ISST: PUNIT device mapping with Sub-NUMA clustering
ff455f7fbce7 net/mlx5: Devcom, serialize devcom registration
69966bce28da net/mlx5e: Fix deadlock in tc route query code
1c4e3cf8944f net/mlx5: devcom only supports 2 ports
79ea1a12fb9a bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
1f06b2a60445 power: supply: bq24190: Call power_supply_changed() after updating input current
8c6f881dc13b power: supply: core: Refactor power_supply_set_input_current_limit_from_supplier()
1f9367a890ac power: supply: bq27xxx: After charger plug in/out wait 0.5s for things to stabilize
75a7e9de60a2 power: supply: bq27xxx: Ensure power_supply_changed() is called on current sign changes
e4c708a9bbde power: supply: bq27xxx: Move bq27xxx_battery_update() down
2288fa1ae9b1 power: supply: bq27xxx: expose battery data when CI=1
(From OE-Core rev: 44262f31928a20a25b4c4a54c3b76a788cc20216)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
(cherry picked from commit acb7f13dd673b15706f56a6b12ab4637a54e89f8)
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.