summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: bitbake-setup: clarify that default answer to prompts is noPaul Gortmaker2025-10-041-3/+3
| | | | | | | | | | | | | | | | It is common practice to put the default choice in upper case for yes/no interactive prompts, so that when people just hit enter, they know what they are getting. An example that linux users are probably familiar with is "sensors-detect" from the "lm-sensors" package. Unify all the prompts to be the same and indicate that the default answer from hitting enter is a no with an upper case N. No functional changes. (Bitbake rev: c7b1a34a25a386426218d63d2aeba0e7c6ecf5b0) Signed-off-by: Paul Gortmaker <paulg@kernel.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: allow using {THISDIR}/my-layerYoann Congal2025-10-042-5/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This implement the ability to use "{THISDIR}/my-layer" in the "bb-layers" list. "{THISDIR}" is remplaced by the directory containing the configuration file. In small projects, we try to keep the setup a simple as possible: a single git repo containing both the build confguration (e.g. a bitbake-setup configuration file) and the meta layer with project recipes/machine/distro. This change allows this kind of setup: ├── meta-my-project/ # the project layer └── my-project.conf.json # the bb-setup configuration file by writing, in my-project.conf.json: "bitbake-setup": { "configurations": [{ "bb-layers": [ "{THISDIR}/meta-my-project" Note: in this case meta-my-project is not present as a "source", so, not handled by bb-setup update/status. It is expected of the user to handle this on their own (is our case, a simple git workflow). (Bitbake rev: 61fbdeb358979bb13c9e50d807f43e554497dc9c) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: lib/bb/tests/setup.py: unset BBPATH to ensure isolation from the ↵Alexander Kanavin2025-10-041-0/+5
| | | | | | | | | | | | existing bitbake environment bitbake-setup deduces top directory from BBPATH, which, if set, interferes with the tests' own setup. (Bitbake rev: ca21545bb847138d75d985d6d7eb0dc9b14550be) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: lib/bb/tests/setup.py: define test parameters in a single dictionaryAlexander Kanavin2025-10-041-3/+7
| | | | | | | | | This makes maintaining and extending them easier. (Bitbake rev: d4379bb791b8961538a4d445d5f956fafffbb0e5) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: dash support for init-build-env scriptYoann Congal2025-10-041-7/+8
| | | | | | | | | | | | | | | | | | | | | | Being minimalist, dash does not support the (non-POSIX) feature of passing an argument while sourcing a script. Like in . <some path>/oe-init-build-env <build dir> With dash, one must use: set <build dir> # puts <build dir> in $1 cd <some path> . ./oe-init-build-env # can only be called from its directory in dash To do this: * Instead of a symlink to oe-init-build-env, keep a symlink to the directory containing it (called "oe-init-build-env-dir") * Generate a init-build-env script that dash can source using the above snippet. (Bitbake rev: d77386e6ab155081ff3bef2aab413ff8061e83a5) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: suggest "." instead of "source"Yoann Congal2025-10-041-1/+1
| | | | | | | | | | | | "." is in POSIX standard[0], whereas "source" is only supported in more feature-full shells (bash, zsh, ...) [0]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#dot (Bitbake rev: 3c5f04343b30efcf53d13f13203c5b0f3a518b99) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: improve robustness of loading/writing settingsAlexander Kanavin2025-10-041-3/+3
| | | | | | | | | | | | | | | Particularly: - ensure global settings command line argument is always expanded to full path - ensure any errors that happen when loading settings are reported at that point, otherwise we get an empty dictionary and cryptic key errors later (Bitbake rev: b3f3ea52e90fb2036074cc88fd00496eb995346d) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add support for specifying branches in repo checkoutsAlexander Kanavin2025-10-044-7/+23
| | | | | | | | | | | | | | | | | | | | Previously bitbake-setup was checking out 'detached commits' using fetcher's nobranch feature, as that is the only option when only a revision is in the config. Branches are optional, but beneficial, as - checkout directory will be on a branch, making it easier for users to understand where they are if they need to make changes (also bitbake will print branch information instead of saying 'HEAD:sha'). - supply chain security! Enforcing a branch means any specified revision has to be on it, and no one can sneak in (accidentally or deliberately!) some dangling commit, or something from their private branch in the same repo. (Bitbake rev: 14dd5f53913419a6c26c0b809a592bd19ae8495a) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: Improve the already initialized testRichard Purdie2025-10-041-2/+2
| | | | | | | | | If the directory already exists but hasn't been setup, the current test can fail so improve it. (Bitbake rev: f8cc590403212886cc5ea19fe1e78dcd3438b612) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: Switch to internal default registry filesRichard Purdie2025-10-041-1/+1
| | | | | | | | | Switch the url to be the default internal registry rather than a private repo which was intended for testing. (Bitbake rev: dd1841a7c3edc2749924370c307ff40ec65f0fe1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Add default registry config for OpenEmbedded's nodistro and Yocto ↵Richard Purdie2025-10-042-0/+124
| | | | | | | | | | | | | | | Project's poky Rather than forcing every user to have to access a separate repository for data for some key defaults, add those for nodistro and poky. This gives us some commonly used setups and also something to test against too. We will need to come up with a criteria for adding these, most likely based on community usage/demand with the OE TSC governing that policy. (Bitbake rev: ce6561608904e971a5cf9214a68391ea7fccc6b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: Allow local registry pathsRichard Purdie2025-10-041-4/+9
| | | | | | | | | | It is useful for bitbake-setup to support local paths without access through the fetcher so that internal data to the bitbake repository can be used as a default. (Bitbake rev: 5b8cd9d2156ef6bdd4c6e61130fadc0ff85f7f1f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: adjust the error message about missing websockets module to ↵Alexander Kanavin2025-10-041-1/+4
| | | | | | | | | mention bitbake-setup (Bitbake rev: d857ed2044c8153c69bd3e275cfc8a9b6a8cdc5e) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add 'install-buildtools' commandAlexander Kanavin2025-10-042-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This basically calls install-buildtools from oe-core/poky, but it ensures via command line parameters that the installation location is stable and the downloads are preserved for reproducibility: $ bin/bitbake-setup install-buildtools Loading settings from /home/alex/bitbake-builds/bitbake-setup.conf ====== Buildtools archive is downloaded into /home/alex/bitbake-builds/yocto-master-testing/buildtools-downloads/20250319141333 and its content installed into /home/alex/bitbake-builds/yocto-master-testing/buildtools ... (output from install-buildtools script) ====== It also detects when buildtools are already installed, and will direct users what to do: ====== alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-setup install-buildtools Loading settings from /home/alex/bitbake-builds/bitbake-setup.conf Buildtools are already installed in /home/alex/bitbake-builds/yocto-master-testing/buildtools. If you wish to use them, you need to source the the environment setup script e.g. $ . /home/alex/bitbake-builds/yocto-master-testing/buildtools/environment-setup-x86_64-pokysdk-linux You can also re-run bitbake-setup install-buildtools with --force option to force a reinstallation ====== This commits includes fixes by Gyorgy Sarvari <skandigraun@gmail.com> https://github.com/kanavin/bitbake/pull/2 (Bitbake rev: 9fb564b720ff5d29a245ec900c8996da7f5f24a6) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add tests to bitbake-selftestAlexander Kanavin2025-10-042-0/+267
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Run like this: alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-selftest -v bb.tests.setup test_setup (bb.tests.setup.BitbakeSetupTest.test_setup) ... ok ---------------------------------------------------------------------- Ran 1 test in 9.223s OK The test does a basic run-through of init, then status/update on an unchanged configuration, then status/update on a configuration changed via new commits to the test layer, then status/update on configuration changed via the top level json config file. Note that nothing whatsoever is fetched from the network; the test relies entirely on synthetic data contained inside itself, including minimal stubs for oe-setup-build and bitbake-config-build. This data is used to create temporary git repositories then clone them via local filesystem URIs. Later on this can be supplemented by an oe-selftest that tests bitbake-setup against real config files in the official configuration repository and real layers, templates and fragments. (Bitbake rev: 59ec7e2ac56e364bae39ccb5e884c447a5379531) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add the initial implementationAlexander Kanavin2025-10-041-0/+809
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Preamble ======== The latest iteration of this patchset is available at https://github.com/kanavin/bitbake I recommend taking the patches from there to ensure that you are not trying out outdated code. For the rationale and design guidelines please see this message: https://lists.openembedded.org/g/openembedded-architecture/message/1913 Left out for now but will be done later: - official configuration repository - documentation Amble *scratch* HOWTO ===================== 1. If you don't know where to start, run 'bitbake-setup init'. Bitbake-setup will ask a few questions about available configuration choices and set up a build. Note: 'init' sub-command can also take a path or a URL with a configuration file directly. You can see how those files look like here: https://github.com/kanavin/bitbake-setup-configurations 2. You can then source the bitbake environment and run bitbake to perform builds as usual: $ . /home/alex/bitbake-builds/yocto-master-options-poky-distro_poky-machine_qemux86-64/build/init-build-env Also, subsequent status/update commands will not require a separate --build-dir argument telling bitbake-setup where the build is. 3. To check if the build configuration needs to be updated, run: === $ bin/bitbake-setup status ... Configuration in /home/alex/bitbake-builds/poky-alex/ has not changed. === If the configuration has changed, you will see the difference as a diff. ... - "rev": "akanavin/sstate-for-all" + "rev": "akanavin/bitbake-setup-testing" ... If the configuration has not changed, but layer revisions referred to it have (for example if the configuration specifies a tip of a branch), you will see that too: === ... Layer repository git://git.yoctoproject.org/poky-contrib checked out into /home/alex/builds/poky-alex/layers/poky updated revision akanavin/sstate-for-all from 6b842ba55f996b27c900e3de78ceac8cb3b1c492 to aeb73e29379fe6007a8adc8d94c1ac18a93e68de === 4. If the configuration has changed, you can bring it in sync with: $ bin/bitbake-setup update Note that it will also rename/preserve the existing build/conf directory, and print changes in bitbake configuration (diff of content of build/conf/) if that has changed. I can't at the moment think of anything more clever that is also not much more brittle or complex to implement, but open to suggestions. Terminology =========== - 'top directory' means the place under which bitbake-setup reads and writes everything. bitbake-setup makes a promise to not touch anything outside of that, unless otherwise directed to by entries in settings (currently there is one such setting for fetcher downloads for layers and config registries). Top directory can be selected by an environment variable, a command line option, or otherwise assumed to be ~/bitbake-builds/. If BBPATH is in environment (e.g. we are in a bitbake environment), then the top directory is deduced from that and doesn't need to be specified by hand. - 'settings' means bitbake-setup operational parameters that are global to all builds under a top directory. E.g. the location of configuration registry, or where the bitbake fetcher should place the downloads (DL_DIR setting). Settings are stored in a .conf file in ini format just under the top directory. - 'build' means a tree structure set up by 'bitbake-setup init', consisting of, at least, a layers checkout, and a bitbake build. It maps 1:1 to the json data it was constructed from, which is called 'build configuration'. Build configurations are constructed from generic configurations that may involve making one or more choices about available options in them. Generic configurations are files, URLs or are obtained from git repositories called 'config registries', in which case they can be listed with 'bitbake-setup list'. There can be multiple 'builds' under a top directory. Here are two example generic configurations that showcase this: https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-options.conf.json https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-nested-configs.conf.json - 'bitbake-setup status' will tell if a build is in sync with the generic configuration it was made from. 'bitbake-setup update' will bring a build in sync with a configuration if needed. - 'bitbake build' means a particular sub-tree inside a build that bitbake itself operates on, e.g. what is set in BBPATH/BUILDDIR by oe-init-build-env. conf/* in that tree is 'bitbake configuration'. Bitbake configurations are constructed from templates and fragments, with existing mechanisms provided by oe-core. The configuration file format is specified such that other mechanisms to set up a bitbake build can be added; there was a mention of ability to specify local.conf content and a set of layers directly in a configuration. I think that scales poorly compared to templates and fragments, but I made sure alternative ways to configure a bitbake build are possible to add in the future :) - 'source override' is a json file that can be used to modify revisions and origins of layers that need to be checkout into a build (e.g. when master branches need to be changed to master-next for purposes of testing). Such a file is specified with a command-line option to 'init' and an example can be seen here: https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-next.override.json This commit includes fixes by Ryan Eatmon <reatmon@ti.com> https://github.com/kanavin/bitbake/pull/1 Gyorgy Sarvari <skandigraun@gmail.com> https://github.com/kanavin/bitbake/pull/2 Johannes Schneider <johannes.schneider@leica-geosystems.com> https://github.com/kanavin/bitbake/pull/3 https://github.com/kanavin/bitbake/pull/5 (Bitbake rev: bf3542076cdd751da9de8745aa3f351f5c6b0c5f) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: parse: Make include_all raise a parse error for absolute pathsPeter Kjellerstedt2025-10-042-0/+4
| | | | | | | | | It makes no sense to use an absolute path with include_all. (Bitbake rev: a39d1d5df740824d40c4d8e7f4199ccc518592e0) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: parse: Make include_all support empty variable expansionsPeter Kjellerstedt2025-10-043-5/+9
| | | | | | | | | | | | | include and require support empty variable expansions, typically used with conditional expansions. However, include_all does not, and instead reports an error for the first path in BBPATH. Rewrite include_all so that its behavior matches include and require. (Bitbake rev: 010928ceac48b20e6ab530f8e256b72201b778ec) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tools/build-docs-container: update with newly supported distrosAntonin Godard2025-10-031-8/+14
| | | | | | | | | | | Update the build-docs-container file with newly supported distributions. These were all able to install packages and build the docs (including the pdf) properly. (From yocto-docs rev: 09c7800333b17b21e50d2a089a3ae1b123697243) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* set_versions.py: fix subprocess.run call for older distrosAntonin Godard2025-10-031-1/+1
| | | | | | | | | | | Like in 28850c974a38 ("set_versions.py: use backward-compatible python argument in run"), replace the capture_output options by Python <3.7 compatible ones. (From yocto-docs rev: 6e1f4c18a13f369423599529a6960da5e3947d01) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* docs: add util-linux-script package for Fedora 42+Adrian Freihofer2025-10-031-1/+1
| | | | | | | | | | | | | | | | | | | | | Fedora 42 split the script utility from util-linux into a separate util-linux-script package. This change adds conditional installation of util-linux-script for Fedora 42 and later versions. https://src.fedoraproject.org/rpms/util-linux/c/5a2471d6e5b0055cb607b30dc2e9613b312ffb74?branch=rawhide The package is added conditionally using rpm macro evaluation to maintain compatibility with older Fedora versions where script was included in the base util-linux package. Note that different distributions handle this differently - for example, Debian provides the script utility in a separate bsdutils package rather than in util-linux. (From yocto-docs rev: 22e28e817d2c9b49d9fedbb93b08874cec1fa3d3) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual/system-requirements.rst: update supported distributionsAntonin Godard2025-10-031-2/+3
| | | | | | | | | After 837a650aac17 ("poky: Update SANITY_TESTED_DISTROS") in meta-yocto. (From yocto-docs rev: 4e7ce89ff91f5fa7ade1feb7be96f898b56068ed) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual/variables.rst: fix the description of STAGING_DIRAdam Blank2025-10-031-1/+1
| | | | | | | | | | | There is no single "recipe-sysroots" directory, but rather many "recipe-sysroot*" directories. (From yocto-docs rev: f2d6e228409cb1dd1dbf339c405699ac6d3900be) Signed-off-by: Adam Blank <adam.blank.g@gmail.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add documentation on fragmentsAntonin Godard2025-10-036-0/+537
| | | | | | | | | | | | | | | - terms.rst: Provide the definitions of a Configuration Fragment and a Built-in Fragment. - ref-manual: Add a quick reference guide on bitbake-config-build, and list the available fragments in OE-Core. Document the underlying variables related to fragments in the glossary. - dev-manual: give instructions on how to create new custom fragments. (From yocto-docs rev: 0820b71c830cab4151b0219b6d4013c41f461c6e) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual/structure: document the auto.conf fileAntonin Godard2025-10-031-0/+9
| | | | | | | | | | Add documentation for auto.conf, which is used by external tools for automatically setting variables. (From yocto-docs rev: 134e54a75e0144c4629f702c6f43e92ed1f12dce) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual/building.rst: add note about externalsrc variables absolute pathsTalel BELHAJ SALEM2025-10-031-0/+5
| | | | | | | | (From yocto-docs rev: 33166d70b6ad093bd95ffccafc0b07820682f656) Signed-off-by: Talel BELHAJ SALEM <bhstalel@gmail.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tools: build-docs-container: remove comment for unsupported distrosQuentin Schulz2025-10-031-3/+0
| | | | | | | | | | | Ubuntu 18.04 and 20.04 are not supported distros, so let's remove the comment listing the reason we don't support them. (From yocto-docs rev: 9ff31ed417bc7cd80f8bde39372091e40e36b678) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual/variables.rst: fix the description of KBUILD_DEFCONFIGAdam Blank2025-10-031-2/+1
| | | | | | | | | | Remove some leftover confusing mention of KMACHINE. (From yocto-docs rev: 582ee9e0b4930aea03255542b3d3913df19af8b0) Signed-off-by: Adam Blank <adam.blank.g@gmail.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-dev/common.rst: fix the in-tree defconfig descriptionAdam Blank2025-10-031-7/+3
| | | | | | | | | | | | | The description of the relation between KBUILD_DEFCONFIG and SRC_URI is reversed. In fact it is the SRC_URI provided defconfig which will be dropped by the kernel-yocto class if both are provided. (From yocto-docs rev: a808420655a0976ba08f013f468cf80f379b1d89) Signed-off-by: Adam Blank <adam.blank.g@gmail.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: do not require CONF_VERSION (e.g. local.conf version) to ↵Alexander Kanavin2025-10-021-1/+7
| | | | | | | | | | | | | | | | | | be set The version checks for local.conf/site.conf/bblayers.conf are all optional, and aren't enforced (by insane class) if the versions aren't set. As bitbake-setup writes out a blank local.conf, it doesn't put a version in it either. Also, esdk bundle has a fixed set of layers and is not at risk of needing to update its own local.conf. The same condition is already in place for esdk's bblayers.conf for similar reasons. (From OE-Core rev: d83ff28157aaa9322f98b8da5dd50b562085085a) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ghostscript: upgrade 10.05.1 -> 10.06.0Vijay Anusuri2025-10-023-70/+66
| | | | | | | | | | | | | | | | | | | | Dropped 0001-Bug-708160-Fix-compatibility-with-C23-compilers.patch Added 0001-Fix-32-bit-build.patch to fix 32-bit archs build Added fPIC flag needed to prevent a linker error during the build process. This upgrade addresses CVEs: CVE-2025-59798, CVE-2025-59799, CVE-2025-59800, CVE-2025-59801 Changelog: https://ghostscript.readthedocs.io/en/gs10.06.0/News.html (From OE-Core rev: 0144e22195394ce2b21b476a1dcfde9129eaf615) Signed-off-by: Vijay Anusuri <vanusuri@mvista.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.py: replace all files unconditionally when copy debug sourcesChangqing Li2025-10-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is for fixing reproducible issue for package like: intel-speed-select-src. For intel-speed-select, one of the debug sources is /usr/src/debug/intel-speed-select/1.0/include/linux/thermal.h, file include/linux/thermal.h under ${S} (kernel-sources) link file include/linux/thermal.h under ${B}, which link to ${S}/include/uapi/linux/thermal.h During copy debug sources, sources under ${S} copied first, then sources under ${B} is copied. mtime of ${S}/include/linux/thermal.h and ${S}/include/uapi/linux/thermal.h are decided by when it is fetched, so it is not determinate, maybe same or different. For cpio, if the in file is older than or the same as the exist file, cpio will not replace the exist file with warning "cpio: xxx not created: newer or same age version exists". And this will cause intel-speed-select-src maybe not reproducible. And option '-u' for cpio, first, this will make the copied file determistic. Second, source files under ${B} should have higher priority then ${S}, it may be generated during build, the target is more likely to use this file. (From OE-Core rev: 8898f97b4acc9d5c2c6583c91d05327f9093133e) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: Fix FILES for intel firmwareRyan Eatmon2025-10-021-26/+26
| | | | | | | | | | | | | | | | The 20250917 version is installing the firmware files into the /usr/lib/firmware/intel directory and symbolic links to those files under /usr/lib/firmware. FILES needs to be updated to correctly package all of the files into the right packages. Without this we get a dependency from the linux-firmware-iwlwifi-* and linux-firmware-qat packages back to linux-firmware which means you have to install ALL of the drivers when you depend on the specific package. (From OE-Core rev: d5144f7031f1f25bb769aed860c45b1fe00ddba4) Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: build with MinSizeRelRoss Burton2025-10-021-3/+3
| | | | | | | | | | | | | | | | | | | This is the recommended build configuration upstream unless speed is the ultimate goal. They say it's almost as fast as Release (-O3) but a lot smaller on disk: clang-libclang-cpp: PKGSIZE changed from 71729568 to 49368816 (-31%) clang-libllvm: PKGSIZE changed from 83015559 to 56662823 (-32%) clang-tidy: PKGSIZE changed from 15861679 to 9956175 (-37%) clang-tools: PKGSIZE changed from 6865635 to 5374691 (-22%) clang: PKGSIZE changed from 29693308 to 22697548 (-24%) libclang: PKGSIZE changed from 40087018 to 26966218 (-33%) (From OE-Core rev: ea9b33f7c12f773830ec860ae817a3ed1368612b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: fix reproducibility issue in LLVMConfig.cmakeRoss Burton2025-10-022-0/+30
| | | | | | | | | | | | | | | | | | | The LLVMConfig.cmake file is mostly LLVM configuration, but it also specifies if some Python modules (needed by the opt-viewer tool) were present on the build host. This is host contamination and a source of non-determinism, so remove it from the installed file. A ticket has been filed upstream to resolve this: https://github.com/llvm/llvm-project/issues/161199 (From OE-Core rev: 916c074a136e8e07f388c2c41d197a15a4c50022) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: use EXTRA_OECMAKE +=Ross Burton2025-10-023-13/+13
| | | | | | | | | | Don't assign EXTRA_OECMAKE so that the include files can set defaults. (From OE-Core rev: 5ad8d6ddf7a1ada37ad1070a3d3347c7f6d57148) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gn: Add recipeKhem Raj2025-10-023-0/+54
| | | | | | | | | | | | | | | | | | | | | | | gn is a commonly used build tool to generate ninja files, used in a lot of recipes e.g. chromium, qtwebengine, perfetto, hafnium etc. these recipes come from different layers e.g. meta-qt6/meta-arm/meta-oe since not all layers depend on meta-oe ( meta-arm does not ), its not a possible option. Given the usecases, putting it in core will benefit the ecosystem and reduce some duplication. This recipe is taken from meta-arm Disable maybe-initialized is a gcc specific option as error Disable format warnings as errors, it adds -Wno-format explictly in its build system (From OE-Core rev: e8dbf41f1f40ae3a5f9641429cad974f716f1f3e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Update to tip of trunkKhem Raj2025-10-021-1/+1
| | | | | | | | | | | | | | Brings * 0ccaf057 printf: fix buffer overflow in floating point decimal formatting * 0b86d60b riscv: fix setjmp assembly when compiling for ilp32f/lp64f. * f6944eb3 powerpc[64]: fix missing ctr and xer regs in syscall asm clobberlists * a6244de1 fix erroneous definition of IN6_IS_ADDR_V4COMPAT (From OE-Core rev: 9ba3fbf1d4ed63b22d108d4d2beebcbcfa352884) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-c: update 0.10.15 -> 0.10.16Deepesh Varatharajan2025-10-022-293/+283
| | | | | | | | (From OE-Core rev: d3cf1b37ce8686dc0781aff9bf35f4487c2c76a6) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity: Update minimum gcc version to 10.1Antonin Godard2025-10-021-6/+3
| | | | | | | | | | | | | | | | | | | Since commit 19004950ad56 ("sanity: Check if the C++ toolchain supports --std=gnu++20") host GCC must support "--std=gnu++20", which became available in 10.1. This is already reflected in the documentation [1] but not here. Update the sanity check on GCC and raise the minimum version to 10.1. Remove the dead link to www.softwarecollections.org. [1]: https://git.yoctoproject.org/yocto-docs/commit/?id=0e538c102bfcb7184c76c2401e8cb878168c4434 Cc: Yoann Congal <yoann.congal@smile.fr> (From OE-Core rev: 871cc04305fe7483a4c256f38fa63a67cef82183) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: backport the topology rename patchDmitry Baryshkov2025-10-022-1/+41
| | | | | | | | | | | | Backport the patch from the trunk, renaming topology file for one of Qualcomm boards in order to reduce possible compatibility issues. Cc: Vivek Puar <vpuar@qti.qualcomm.com> (From OE-Core rev: ee1600aff7ed3c18f5cb512ca069ff564063744e) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: fix Bluetooth LE audio regressionGuðni Már Gilbert2025-10-022-0/+30
| | | | | | | | | | Backport a fix for a regression introduced in 5.84 which breaks Bluetooth LE audio (From OE-Core rev: 2b675c5cbfcaa7a5918ddd4a13400be5be60b3e6) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: Increase the maximum group name length to 32 (the default)Peter Kjellerstedt2025-10-021-1/+0
| | | | | | | | | | | | | | | Back in 2014, the maximum group name length was increased from 16 (the default) to 24. Since then, the default has increased to 32, and our configuration is now actually a decrease in maximum group name length. Remove the configuration to use the default instead, which aligns the maximum group name length with the maximum user name length. (From OE-Core rev: 02c98c3b199bfe3c6b8acd6e2ebf13088564c351) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: upgrade to 1.9.1Ross Burton2025-10-026-103/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes in this release: 751b09390 Bump versions to 1.9.1 for release d0abb2133 Boost python must have a library component. e6732c220 Check for header only Boost libraries. 08429813b get_llvm_tool_names: add llvm 21 f3b383217 docs: fix pre-1.8 order for per-subproject options a2d395498 Revert "test cases: do not pass global option on command line" d0f82544e Revert "tests: skip test common/223 in the -Ddefault_library=... jobs" 2abdb2f0b options: put back in place 1.7 ordering of opt=value vs subp:opt=value 83cbc65c2 Fix not passing user option args to scan-build build e746db0b4 Document internal dep support in pkgconfig.generate `requires` arg f6ab732b7 msetup: not-found subprojects do not have known options 5d21e653a utils: make .wraplock optional d1e219cb8 Fix Cygwin test failure. 0fc77e2d7 coredata: do not write None to cmd_line.txt 533ba5cb3 options: do not raise exception for unknown options in -U command ae822d1d4 test cases/common/32 has header: disable undef with libcxx c58f0d951 rustdoc: skip --crate-type option b8e0e9d3d fix transient failure on rust/12 bindgen 75cf757b7 coredata: check for per-subproject compiler and linker arguments a747c4ea8 coredata: check for per-subproject compiler options Drop the two backported patches. (From OE-Core rev: 3acddf6cae1449591227b2f07fed13195cad0b82) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xkeyboard-config: Turn absolute symlinks into relativeKhem Raj2025-10-021-1/+1
| | | | | | | | | | | | | | | | | | | Native builds encode symlinks pointing to absolute paths into build native sysroot which gets into sstate artifacts and an error is rightly generated ERROR: xkeyboard-config-native-2.45-r0 do_populate_sysroot: sstate found an absolute path symlink /mnt/b/yoe/master/build/tmp/work/x86_64-linux/xkeyboard-config-native/2.45/sysroot-destdir/mnt/b/yoe/master/build/tmp/work/x86_64-linux/xkeyboard-config-native/2.45/recipe-sysroot-native/usr/share/X11/xkb pointing at /mnt/b/yoe/master/build/tmp/work/x86_64-linux/xkeyboard-config-native/2.45/recipe-sysroot-native/usr/share/xkeyboard-config-2. Please replace this with a relative link. ERROR: xkeyboard-config-native-2.45-r0 do_populate_sysroot: Failing task due to absolute path symlinks Turn these symlinks to be relative inside D which will reflect correclty without need for absolute path prefix Suggested-by: Zoltán Böszörményi <zboszor@gmail.com> (From OE-Core rev: 811d4a9186c520e860877da536f5544daac9a2a9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2025-10-011-1/+1
| | | | | | (From OE-Core rev: 9f1a1fc1a163e74602d8a359483087f1117f23c2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky: Update SANITY_TESTED_DISTROSRichard Purdie2025-10-011-1/+3
| | | | | | | | Add Fedora 52, Debian 13 and Ubuntu 25.04, drop Ubuntu 24.10. (From meta-yocto rev: 837a650aac17598dd2b0113f47c9058f2162cd34) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust-target-config: Update the data layout for ppc64 targets.Deepesh Varatharajan2025-10-011-2/+2
| | | | | | | | | | | Rust commit for updating the data layouts: https://github.com/rust-lang/rust/commit/0680155a171d47772302fc4da4cbbfa466378d81 (From OE-Core rev: cf1972b7b96bb38b48e90654a8c840568e4646cf) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.12: update CVE exclusions (6.12.49)Bruce Ashfield2025-10-011-8/+56
| | | | | | | | | | | | | | | | | | Data pulled from: https://github.com/CVEProject/cvelistV5 1/1 [ Author: cvelistV5 Github Action Email: github_action@example.com Subject: 1 changes (1 new | 0 updated): - 1 new CVEs: CVE-2025-11135 - 0 updated CVEs: Date: Mon, 29 Sep 2025 01:40:51 +0000 ] (From OE-Core rev: 13acb9570660dde8f1cccb045981b646acb44aea) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.12: update to v6.12.49Bruce Ashfield2025-10-013-19/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating linux-yocto/6.12 to the latest korg -stable release that comprises the following commits: da274362a7bd Linux 6.12.49 6553fdf0f7d4 minmax.h: remove some #defines that are only expanded once cf5fe0b36f10 minmax.h: simplify the variants of clamp() 5c2b06b31da6 minmax.h: move all the clamp() definitions after the min/max() ones 5f6818002047 minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp() e94ce277b568 minmax.h: reduce the #define expansion of min(), max() and clamp() ab58f71b8fdf minmax.h: update some comments d9c5ccf6b69b minmax.h: add whitespace around operators and after commas 63fd831aa5dc rtc: pcf2127: fix SPI command byte for PCF2131 backport 207fa0d49522 xhci: dbc: Fix full DbC transfer ring after several reconnects 490f1ca013b5 xhci: dbc: decouple endpoint allocation from initialization 9b28ef1e4cc0 usb: xhci: remove option to change a default ring's TRB cycle bit e5051c055926 usb: xhci: introduce macro for ring segment list iteration c839be6df4da mptcp: pm: nl: announce deny-join-id0 flag 34f351c0fa95 mm/gup: check ref_count instead of lru before migration 096c5b1fde51 mm: add folio_expected_ref_count() for reference count calculation 23da4e0bb2a3 vmxnet3: unregister xdp rxq info in the reset path ca8938704142 KVM: SVM: Set/clear SRSO's BP_SPEC_REDUCE on 0 <=> 1 VM count transitions e5a3331a2e98 x86/bugs: KVM: Add support for SRSO_MSR_FIX f9c6aec2a6dd x86/bugs: Add SRSO_USER_KERNEL_NO support 0a3ac13d8686 platform/x86: asus-wmi: Re-add extra keys to ignore_key_wlan quirk 7228ed156377 platform/x86: asus-wmi: Fix ROG button mapping, tablet mode on ASUS ROG Z13 a89c34babc2e io_uring: fix incorrect io_kiocb reference in io_link_skb 922338efaad6 smb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path 24c1106504c6 crypto: af_alg - Set merge to zero early in af_alg_sendmsg 6ae90a2baf92 smb: client: let smbd_destroy() call disable_work_sync(&info->post_send_credits_work) b814660334bb smb: client: fix filename matching of deferred files ea5cbcecd54d drm/xe: Fix a NULL vs IS_ERR() in xe_vm_add_compute_exec_queue() f108c98c7005 drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path 0da73f782769 drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ 503de75db426 drm/xe/tile: Release kobject for the failure path 22814abfd961 ASoC: Intel: catpt: Expose correct bit depth to userspace b51ded0f604e ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message e5c10cec7a1b ASoC: wm8974: Correct PLL rate rounding 987b1d5e39b9 ASoC: wm8940: Correct typo in control name ccba708502b6 ASoC: wm8940: Correct PLL rate rounding 695673eb5711 io_uring/kbuf: drop WARN_ON_ONCE() from incremental length check 93e9d0293d3b io_uring/msg_ring: kill alloc_cache for io_kiocb allocations e6b2b4a0ffd8 io_uring: include dying ring in task_work "should cancel" state d7a38ee4f0be io_uring: backport io_should_terminate_tw() 9b71bfefc405 io_uring/cmd: let cmds to know about dying task 9ffc5f132a35 ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx acab5c56a6fa selftests: mptcp: avoid spurious errors on TCP disconnect 2b5b0674686f selftests: mptcp: connect: catch IO errors on listen side ca261278c6b7 mptcp: propagate shutdown to subflows when possible 60b07b9f6093 rds: ib: Increment i_fastreg_wrs before bailing out 21ba85d9d508 net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer 232e74984061 drm/amd/display: Allow RX6xxx & RX7700 to invoke amdgpu_irq_get/put 2ae6d79a769b KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active bd5524ec7155 mmc: mvsdio: Fix dma_unmap_sg() nents value 6dbac7d814a7 ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S 9c534dbfd172 ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed d1c96316e4c1 ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface bf46ed89bf24 btrfs: tree-checker: fix the incorrect inode ref size check cd92c8ab336c iommu/amd/pgtbl: Fix possible race while increase page table level c023b4f4444f iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() 1e68a5f046e9 LoongArch: Check the return value when creating kobj 05a76baf2700 LoongArch: Align ACPI structures if ARCH_STRICT_ALIGN enabled 382f5ff57010 LoongArch: vDSO: Check kcalloc() result in init_vdso() 040f278cc1a5 LoongArch: Fix unreliable stack for live patching b6f29fa5f603 objtool/LoongArch: Mark special atomic instruction as INSN_BUG type 89d40cc647da objtool/LoongArch: Mark types based on break immediate code 1766f14c8f97 LoongArch: Update help info of ARCH_STRICT_ALIGN cbb8cd66d0bc mm: revert "mm: vmscan.c: fix OOM on swap stress test" f6e161f3fa99 gup: optimize longterm pin_user_pages() for large folio f8f64254bca5 dm-stripe: fix a possible integer overflow cb58eaad2235 dm-raid: don't set io_min and io_opt for raid1 7061e566ce5d power: supply: bq27xxx: restrict no-battery detection to bq27000 f91359651678 power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery 9aee87da5572 crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg 1adc72411f3d nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* 9644798294c7 ksmbd: smbdirect: verify remaining_data_length respects max_fragmented_recv_size 8be498fcbd5b ksmbd: smbdirect: validate data_offset and data_length field of smb_direct_data_transfer e97c45c770f5 perf/x86/intel: Fix crash in icl_update_topdown_event() ff27e23b311f octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() 6e33a7eed587 cnic: Fix use-after-free bugs in cnic_delete_task acf8d06b8b97 net: liquidio: fix overflow in octeon_init_instr_queue() f07c925bb70e Revert "net/mlx5e: Update and set Xon/Xoff upon port speed set" 208640e6225c tls: make sure to abort the stream if headers are bogus fa4749c06564 tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). 0c691ea3852c octeon_ep: fix VF MAC address lifecycle handling 4c0bfb2dc6ab bonding: don't set oif to bond dev when getting NS target destination d1f3db4e7a3b net/mlx5e: Harden uplink netdev access against device unbind bec504867acc igc: don't fail igc_probe() on LED setup error 610332f7ac20 i40e: remove redundant memory barrier when cleaning Tx descs 80555adb5c89 ice: fix Rx page leak on multi-buffer frames 1644ee7696f3 ice: store max_frame and rx_buf_len only in ice_rx_ring 3e3be7bbe4a5 net: natsemi: fix `rx_dropped` double accounting on `netif_rx()` failure 13e7a6e96076 selftests: mptcp: sockopt: fix error messages 10e54bf7cb6e mptcp: tfo: record 'deny join id0' info bb7a3f09e9d4 selftests: mptcp: userspace pm: validate deny-join-id0 flag 7f5b09cc84e0 mptcp: set remote_deny_join_id0 on SYN recv 9a958802080c bonding: set random address only when slaves already exist 660b2a8f5a30 qed: Don't collect too many protection override GRC elements 5f445eb25990 net/tcp: Fix a NULL pointer dereference when using TCP-AO with TCP_REPAIR 79320035973f dpaa2-switch: fix buffer pool seeding for control traffic 3112c70b2e01 um: Fix FD copy size in os_rcv_fd_msg() 00e98b5a6903 um: virtio_uml: Fix use-after-free after put_device in probe 9c416e76a57f btrfs: fix invalid extref key setup when replaying dentry ded4d207a320 cgroup: split cgroup_destroy_wq into 3 workqueues eed66faed623 pcmcia: omap_cf: Mark driver struct with __refdata to prevent section mismatch 8df33f4d4a0b wifi: mac80211: fix incorrect type for ret 32adb020b0c3 wifi: mac80211: increase scan_ies_len for S1G 814952c1b1ff ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported b146e0434feb nvme: fix PI insert on write 2203ef417044 wifi: wilc1000: avoid buffer overflow in WID string configuration (From OE-Core rev: 28c0056b24be0833bca4c3c86404292d95ad377a) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2026-02-12 23:07:41 +0000