c59873774c
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
0a0beb1f9120 Linux 5.4.135
d2f7b384a74f udp: annotate data races around unix_sk(sk)->gso_size
c72374978b3f perf test bpf: Free obj_buf
17bc942c0b96 bpftool: Properly close va_list 'ap' by va_end() on error
84ed8340941a ipv6: tcp: drop silly ICMPv6 packet too big messages
315033cab379 tcp: annotate data races around tp->mtu_info
41f45e91c92c dma-buf/sync_file: Don't leak fences on merge failure
04b06716838b net: fddi: fix UAF in fza_probe
8aa13a86964c net: validate lwtstate->data before returning from skb_tunnel_info()
8cff7b28ab05 net: send SYNACK packet with accepted fwmark
b7e5563f2a78 net: ti: fix UAF in tlan:remove_one
2b70ca92847c net: qcom/emac: fix UAF in emac:remove
463c0addb4eb net: moxa: fix UAF in moxart_mac_probe
7ac4a6a74e75 net: ip_tunnel: fix mtu calculation for ETHER tunnel devices
d5dc50ca1f7a net: bcmgenet: Ensure all TX/RX queues DMAs are disabled
7ecd40801e5b net: bridge: sync fdb to new unicast-filtering ports
813d45499f51 net/sched: act_ct: fix err check for nf_conntrack_confirm
24973073562f netfilter: ctnetlink: suspicious RCU usage in ctnetlink_dump_helpinfo
c6f4a71153f4 net: ipv6: fix return value of ip6_skb_dst_mtu
9872273b670a net: dsa: mv88e6xxx: enable .rmu_disable() on Topaz
6148ddff2dcb net: dsa: mv88e6xxx: enable .port_set_policy() on Topaz
d73c180e6add dm writecache: return the exact table values that were set
8a85afc6621a mm: slab: fix kmem_cache_create failed when sysfs node not destroyed
f53729b828db usb: cdns3: Enable TDL_CHK only for OUT ep
52b01a808696 f2fs: Show casefolding support only when supported
91d846016729 arm64: dts: marvell: armada-37xx: move firmware node to generic dtsi file
f696cc7f1bc8 firmware: turris-mox-rwtm: add marvell,armada-3700-rwtm-firmware compatible string
e2b28026b861 arm64: dts: armada-3720-turris-mox: add firmware node
f7d1fa65e742 cifs: prevent NULL deref in cifs_compose_mount_options()
06d8a7eb5803 s390: introduce proper type handling call_on_stack() macro
2a47e0719ae7 sched/fair: Fix CFS bandwidth hrtimer expiry type
5b7d065868a6 scsi: qedf: Add check to synchronize abort and flush
0fe70c15f943 scsi: libfc: Fix array index out of bound exception
d7b647d05586 scsi: libsas: Add LUN number check in .slave_alloc callback
863c4bc883d5 scsi: aic7xxx: Fix unintentional sign extension issue on left shift of u8
712e9ed6134f rtc: max77686: Do not enforce (incorrect) interrupt trigger type
199d8ea4c7b1 kbuild: mkcompile_h: consider timestamp if KBUILD_BUILD_TIMESTAMP is set
484193b635a7 thermal/core: Correct function name thermal_zone_device_unregister()
556cf0283035 arm64: dts: imx8mq: assign PCIe clocks
9d3eb68a5385 arm64: dts: ls208xa: remove bus-num from dspi node
e054b361caec firmware: tegra: bpmp: Fix Tegra234-only builds
94d009577033 soc/tegra: fuse: Fix Tegra234-only builds
270a2e9fafea ARM: dts: stm32: move stmmac axi config in ethernet node on stm32mp15
4bc66215bc22 ARM: dts: stm32: fix i2c node name on stm32f746 to prevent warnings
856c753237ae ARM: dts: rockchip: fix supply properties in io-domains nodes
c5bb9cc2ce23 arm64: dts: juno: Update SCPI nodes as per the YAML schema
f572a9139396 ARM: dts: stm32: fix timer nodes on STM32 MCU to prevent warnings
95e795474c81 ARM: dts: stm32: fix RCC node name on stm32f429 MCU
a898aa9f88cc ARM: dts: stm32: fix gpio-keys node on STM32 MCU boards
5c17edaaead7 ARM: dts: am437x-gp-evm: fix ti,no-reset-on-init flag for gpios
3446233096ff ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios
e79e29a4e162 kbuild: sink stdout from cmd for silent build
f817d4677582 rtc: mxc_v2: add missing MODULE_DEVICE_TABLE
0a22b5178276 ARM: imx: pm-imx5: Fix references to imx5_cpu_suspend_info
e20e85639e25 ARM: dts: imx6: phyFLEX: Fix UART hardware flow control
a5b19d33ae22 ARM: dts: Hurricane 2: Fix NAND nodes names
f83535a47ff8 ARM: dts: BCM63xx: Fix NAND nodes names
cb05b84ad7f1 ARM: NSP: dts: fix NAND nodes names
14e3bad3b548 ARM: Cygnus: dts: fix NAND nodes names
587a757afe73 ARM: brcmstb: dts: fix NAND nodes names
a9c32c7aeee6 reset: ti-syscon: fix to_ti_syscon_reset_data macro
b400afa42739 arm64: dts: rockchip: Fix power-controller node names for rk3328
dfb4e8ed0792 arm64: dts: rockchip: Fix power-controller node names for px30
789070f17886 ARM: dts: rockchip: Fix power-controller node names for rk3288
6aaffe6ce8a9 ARM: dts: rockchip: Fix power-controller node names for rk3188
439115ee56d8 ARM: dts: rockchip: Fix power-controller node names for rk3066a
3b4c34728382 ARM: dts: rockchip: Fix IOMMU nodes properties on rk322x
c9d29d62da59 ARM: dts: rockchip: Fix the timer clocks order
d105e15de610 arm64: dts: rockchip: fix pinctrl sleep nodename for rk3399.dtsi
cfe3d29e5cde ARM: dts: rockchip: fix pinctrl sleep nodename for rk3036-kylin and rk3288
79573c64410b ARM: dts: gemini: add device_type on pci
7037876393ce ARM: dts: gemini: rename mdio to the right name
(From OE-Core rev: 5c36549fab7cc27bd2f4f9e8b6be1ec8546d32bd)
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:
http://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: http://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.