Updating to the latest korg -stable release that comprises
the following commits:
0ab06468cbd1 Linux 5.15.114
193c59ba7299 net: phy: mscc: add VSC8502 to MODULE_DEVICE_TABLE
350b95e86ca9 3c589_cs: Fix an error handling path in tc589_probe()
7c2fa3e56d95 regulator: mt6359: add read check for PMIC MT6359
28ebfb74fbf5 firmware: arm_ffa: Set reserved/MBZ fields to zero in the memory descriptors
34b0985ebdfc arm64: dts: imx8mn-var-som: fix PHY detection bug by adding deassert delay
1e7550653680 net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device
a89a69cea44c net/mlx5: Fix error message when failing to allocate device memory
e8a974bbf4a5 net/mlx5: DR, Check force-loopback RC QP capability independently from RoCE
5e0cc0d502d4 net/mlx5: DR, Fix crc32 calculation to work on big-endian (BE) CPUs
792a8233fc01 net/mlx5e: do as little as possible in napi poll when budget is 0
fdf8f33e7d03 platform/mellanox: mlxbf-pmc: fix sscanf() error checking
d5ab5447d910 forcedeth: Fix an error handling path in nv_probe()
ae7c4ec42655 sctp: fix an issue that plpmtu can never go to complete state
ee553694be42 ASoC: Intel: Skylake: Fix declaration of enum skl_ch_cfg
aafa5019e2a3 x86/show_trace_log_lvl: Ensure stack pointer is aligned, again
90314394a16d xen/pvcalls-back: fix double frees with pvcalls_new_active_socket()
ff151810fb95 coresight: Fix signedness bug in tmc_etr_buf_insert_barrier_packet()
24cf11474376 regulator: pca9450: Fix BUCK2 enable_mask
cd41ec23503f fs: fix undefined behavior in bit shift for SB_NOUSER
c2f65991097a firmware: arm_ffa: Fix FFA device names for logical partitions
6a26c62625c5 firmware: arm_ffa: Check if ffa_driver remove is present before executing
f64567bd9566 power: supply: sbs-charger: Fix INHIBITED bit for Status reg
71a9f146b3dc power: supply: bq27xxx: Add cache parameter to bq27xxx_battery_current_and_status()
e98e5bebfcaf power: supply: bq27xxx: Fix poll_interval handling and races on remove
e01820a94aea power: supply: bq27xxx: Fix I2C IRQ race on remove
d21b3448577f power: supply: bq27xxx: Fix bq27xxx_battery_update() race condition
c530f60e5a2e power: supply: mt6360: add a check of devm_work_autocancel in mt6360_charger_probe
0dd4881238bc power: supply: leds: Fix blink to LED on transition
5e4bb063dcaf cifs: mapchars mount option ignored
9b92e2d0eb69 ipv6: Fix out-of-bounds access in ipv6_find_tlv()
bf478c2643ba bpf: Fix mask generation for 32-bit narrow loads of 64-bit fields
79081b3f489a octeontx2-pf: Fix TSOv6 offload
114657365c88 selftests: fib_tests: mute cleanup error message
e06841a2abf9 net: fix skb leak in __skb_tstamp_tx()
8f1512d78b5d ASoC: lpass: Fix for KASAN use_after_free out of bounds
b1bde4b4360c media: radio-shark: Add endpoint checks
43f569fd0699 USB: sisusbvga: Add endpoint checks
da0f4b557682 USB: core: Add routines for endpoint checks in old drivers
387bd0a3af3b udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().
cf3b5cd7127c net: fix stack overflow when LRO is disabled for virtual interfaces
9e12c58a5ece fbdev: udlfb: Fix endpoint check
aee97eec7702 debugobjects: Don't wake up kswapd from fill_pool()
c09a7b6190f5 x86/topology: Fix erroneous smp_num_siblings on Intel Hybrid platforms
a9ffd42eb9ab perf/x86/uncore: Correct the number of CHAs on SPR
277f206bb874 parisc: Fix flush_dcache_page() for usage from irq context
eff115ca949a selftests/memfd: Fix unknown type name build failure
1a98b6e028ee x86/mm: Avoid incomplete Global INVLPG flushes
683bb30c6947 dt-binding: cdns,usb3: Fix cdns,on-chip-buff-size type
647af8a998c2 btrfs: use nofs when cleaning up aborted transactions
7e93fe1d1733 gpio: mockup: Fix mode of debugfs files
3a2d238c5a3a parisc: Allow to reboot machine after system halt
96f8dd0483c8 parisc: Handle kgdb breakpoints only in kernel context
16deb7413ace m68k: Move signal frame following exception on 68020/030
9be921854e98 net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize
1f6ae24e3d5a ASoC: rt5682: Disable jack detection interrupt during suspend
693acaa739dc mmc: sdhci-esdhc-imx: make "no-mmc-hs400" works
7177586e06ff ALSA: hda/realtek: Enable headset onLenovo M70/M90
e6a624451afb ALSA: hda: Fix unhandled register update during auto-suspend period
7716da3fa10b ALSA: hda/ca0132: add quirk for EVGA X299 DARK
c37eb46c613a arm64: Also reset KASAN tag if page is not PG_mte_tagged
291fe3d6f5db ocfs2: Switch to security_inode_init_security()
4badd33929c0 spi: fsl-cpm: Use 16 bit mode for large transfers with even size
28ffe8c84603 spi: fsl-spi: Re-organise transfer bits_per_word adaptation
381e55bffe15 ARM: dts: stm32: fix AV96 board SAI2 pin muxing on stm32mp15
ca338fa8032a watchdog: sp5100_tco: Immediately trigger upon starting.
6312c7cc07f3 dt-bindings: ata: ahci-ceva: Cover all 4 iommus entries
7ef9045fe758 dt-bindings: ata: ahci-ceva: convert to yaml
f19171155305 usb: dwc3: fix gadget mode suspend interrupt handler issue
7919af1dcb8e usb: gadget: Properly configure the device for remote wakeup
(From OE-Core rev: 1c8415175dc89a58e8af604163904cbfbe787edc)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
(cherry picked from commit b83b248e5042dd1e9fdbc4c48be1af188fece1df)
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.