a98dbebf3a
Integrating the following commit(s) to linux-yocto-rt/5.15:
931d5079b9fc Linux 5.15.26-rt34
c5c22d2fdb7b Linux 5.15.25-rt33
6a2e3e6c9401 staging: greybus: gpio: Use generic_handle_irq_safe().
cb17d0820286 net: usb: lan78xx: Use generic_handle_irq_safe().
a4040e8669d8 mfd: ezx-pcap: Use generic_handle_irq_safe().
870d69c5f090 misc: hi6421-spmi-pmic: Use generic_handle_irq_safe().
3718dd5011f4 i2c: cht-wc: Use generic_handle_irq_safe().
1252887f9872 i2c: core: Use generic_handle_irq_safe() in i2c_handle_smbus_host_notify().
5aa6ecf9212a genirq: Provide generic_handle_irq_safe().
1c73db1779a6 Linux 5.15.25-rt32
2e68dcd8d632 Linux 5.15.24-rt31
5ec703bf5ccc net: Write lock dev_base_lock without disabling bottom halves.
15bd5dea95e6 Linux 5.15.21-rt30
88c15a185ab7 Linux 5.15.19-rt29
a70f09a4d312 Linux 5.15.18-rt28
771d328d2646 Linux 5.15.14-rt27
b56e1f0d87ba Linux 5.15.13-rt26
5e8adc085a2b Linux 5.15.12-rt25
ea0f771b9442 Linux 5.15.10-rt24
269b39adfb2c Linux 5.15.7-rt23
(From OE-Core rev: a4198a50971f25e3ef05c9c385c9344dfef24ba9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.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.