Bruce Ashfield e7b915a3ad oeqa/runtime/parselogs: mips: skip sysctl warning
Upstream has shuffled the sysctl registration via the commit:

   commit d4ae80ffa64f87b9c355692b680b603add084e96
   Author: Zhen Ni <nizhen@uniontech.com>
   Date:   Tue Feb 15 19:46:03 2022 +0800

       sched: Move cfs_bandwidth_slice sysctls to fair.c

       move cfs_bandwidth_slice sysctls to fair.c and use the
       new register_sysctl_init() to register the sysctl interface.

       Signed-off-by: Zhen Ni <nizhen@uniontech.com>
       Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

The way that we have to configure our mips qemu platforms
results in an empty sysctl table registration and the following
harmless warnings:

  "failed when register_sysctl_sz sched_fair_sysctls to kernel"
  "failed when register_sysctl_sz sched_core_sysctls to kernel"

Adding them to our list of acceptable dmesg warnings.

(From OE-Core rev: 4cf678858ef6f2c3310ad8f26cac3e7e133d4f0a)

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-08-07 15:47:15 +01:00
2024-02-19 11:34:33 +00:00
2021-07-19 18:07:21 +01:00
2023-10-19 11:31:13 +01:00

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

Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.

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/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

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.

CII Best Practices

Description
No description provided
Readme 251 MiB