4d2d21ef4d
Updating linux-yocto/5.14 to the latest korg -stable release that comprises
the following commits:
b9ed05407395 Linux 5.14.13
d7c187ab28f6 hwmon: (pmbus/ibm-cffps) max_power_out swap changes
e798dcd960a3 io_uring: kill fasync
15571bb5bb64 sched: Always inline is_percpu_thread()
643c519c36dc perf/core: fix userpage->time_enabled of inactive events
15f69a666166 scsi: qla2xxx: Fix excessive messages during device logout
cc07ecaf9a9c scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
21c2e89e7caa scsi: ses: Fix unsigned comparison with less than zero
18d1c5ea3798 drm/amdgpu: fix gart.bo pin_count leak
048389b85643 net: sun: SUNVNET_COMMON should depend on INET
e36444b36ff0 vboxfs: fix broken legacy mount signature checking
5c85a825615a net: bgmac-platform: handle mac-address deferral
af13e6176b25 mac80211: check return value of rhashtable_init
ebb25ff84341 net: prevent user from passing illegal stab size
998e080844c9 hwmon: (ltc2947) Properly handle errors when looking for the external clock
1d0996b0d2b3 m68k: Handle arrivals of multiple signals correctly
4d38fb418f71 pinctrl: qcom: sc7280: Add PM suspend callbacks
9a8a181ed97e mac80211: Drop frames from invalid MAC address in ad-hoc mode
a3ea231aa3f0 netfilter: nf_nat_masquerade: defer conntrack walk to work queue
36f822c301c7 netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic
6c3e84af3944 KVM: arm64: nvhe: Fix missing FORCE for hyp-reloc.S build rule
1fd0252cad6b ASoC: SOF: loader: release_firmware() on load failure to avoid batching
2dd40af15d19 HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs
95cb145dcfc8 netfilter: ip6_tables: zero-initialize fragment offset
f117530a10e0 HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
13e6abfa0b1e ALSA: usb-audio: Unify mixer resume and reset_resume procedure
cb315326664d ALSA: oxfw: fix transmission method for Loud models based on OXFW971
3c13d6e6fc56 ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic
7c2893a12fc0 ext4: correct the error path of ext4_write_inline_data_end()
501f3491d99e ext4: check and update i_disksize properly
(From OE-Core rev: d7eebc956d4fa4353475fda198a656619ae387e4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit a1028453439db361d5f77fa220d77c49bc7a1f82)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.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.