summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* buildstats: Replace 'is' with '==' in python condition check expressionKhem Raj2019-12-151-1/+1
| | | | | | | | | | | | | | | python 3.8 has started to throw this as a warning but usage is wrong see [1], it seems to be working by accident and not design. Fixes SyntaxWarning: "is" with a literal. Did you mean "=="? [1]: https://bugs.python.org/issue34850 (From OE-Core rev: c3cb6bc21f3f84e2ed103b6438516ab85222faa9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libjpeg-turbo: Build reproduciblyJoshua Watt2019-12-151-0/+2
| | | | | | | | | | Configures the options passed to nasm to remove build paths in the generated object files. (From OE-Core rev: 9119a882adbf19df9f47f66cebaa7f730d3e9462) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nasm: Add debug-prefix-map optionJoshua Watt2019-12-153-0/+444
| | | | | | | | | | | Adds an option to nasm to change the prefix for file paths encoded in the object files. This allows builds to be reproducible regardless of the build directory. (From OE-Core rev: ad5c914933c7b38296dcb8bba3c36aed45aacc32) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "go: Reset unneeded GOARCH variables for native recipe"Khem Raj2019-12-151-10/+0
| | | | | | | | | This reverts commit 4825eede606b075d0d529b38d6162999f1dec506. (From OE-Core rev: 18b90967bd367263280ec871be84e67e3eed11fa) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* goarch: Remove target specific dependenciesKhem Raj2019-12-151-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | goarch is used in all classes of recipes ranging from native to target, therefore its best to contain the variables and not spill over into recipe classes where they can adversely affect shared state reuse e.g. go-native currently gets TUNE_FEATURES into dependency chain of referenced variables which means go-native gets rebuilt when we change from qemuarm to qemux86 machine types since TUNE_FEATURES is defined with DEFAULTTUNE which would change as machines are switched These variables are specific to arm/mips/x86 so marking them with appropriate overrides for native recipes will be right thing here Chose 'hardfloat' for mips which is default too, 7 for arm and sse2 for x86 somehow go-native bootstrap compiler (1.4) still needs them so feed commonly used values or defaults. Fixes ERROR: go-native different signature for task do_configure.sigdata between qemux86copy and qemuarm ... List of dependencies for variable TUNE_FEATURES changed from '{'DEFAULTTUNE', 'TUNE_FEATURES_tune-core2-32'}' to '{'DEFAULTTUNE', 'TUNE_FEATURES_tune-armv7vethf-neon'}' changed items: {'TUNE_FEATURES_tune-core2-32', 'TUNE_FEATURES_tune-armv7vethf-neon'} (From OE-Core rev: 83eebf5577dd0a23be937375c1a8a15e3da4fa64) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cronie:fix SRC_URI pathStefano Babic2019-12-151-1/+1
| | | | | | | (From OE-Core rev: 06ce57157a43f5988e1a0c6bc147fec7b55e63ec) Signed-off-by: Stefano Babic <sbabic@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: disable debug output in ptestsAlexander Kanavin2019-12-151-1/+1
| | | | | | | | | | This makes the log very large and breaks the ptest result parser. (From OE-Core rev: 78221af4c0297e0278c042eed390ad0e53f2548a) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez: update 5.50 -> 5.52Alexander Kanavin2019-12-159-982/+16
| | | | | | | | | | | | | Drop a big pile of backports. Disable zsh completions, as they're unlikely to be useful. (From OE-Core rev: dad8cd50bcc4203a65d153dc2445502c1e728975) (From OE-Core rev: 1a31a31a3bd68f027ba0a13f8e66ce92104a4d4c) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: avoid vlock conflict with busyboxHongxu Jia2019-12-151-1/+2
| | | | | | | | | | | | | | | | | | | | | | busybox as well as vlock utility from meta-oe provides vlock utility which can conflict when with kbd if pam is a enabled distro_feature Fixes image build errors update-alternatives: Error: not linking <rootfs>/usr/bin/vlock to /bin/busybox.suid since <rootfs>/usr/bin/vlock exists and is not a link ERROR: yoe-qt5-wayland-image-1.0-r0 do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. (From OE-Core rev: 08636708f6ca677a6ee6c88fa2999c7b70b7d474) Signed-off-by: Khem Raj <raj.khem@gmail.com> The vlock doesn't exist if PAM isn't enabled. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* reproducible_build_simple: inherit podfixRoss Burton2019-12-151-0/+1
| | | | | | | | | | When doing reproducible builds inherit podfix to remove the possibility of differing Perl versions causing manpages to change. (From OE-Core rev: 5dc43edab4787906f2c9f51e51bf78d1dc966286) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* podfix: class to remove Pod::Man versions from manpagesRoss Burton2019-12-151-0/+32
| | | | | | | | | | | | | | Manpages generated by Pod::Man contain the version number, which isn't reproducible if we're using the host Perl to generate manpage. One option is to always depend on perl-native when generating manpages but this is a heavy dependency, so instead strip out the versions in do_install(). (From OE-Core rev: 18d8e5ac689d6eb6098f68ac785f43e9d5f5938a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: ensure we print runqemu output in the event of failurePaul Eggleton2019-12-151-2/+2
| | | | | | | | | | | | If we get here in the code it's because runqemu has failed, this is not a debug situation - we need to see the output, so print it as an error. Fixes [YOCTO #13681]. (From OE-Core rev: c1def38c680d64c992839166bbf9bec51eb0788a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: fix width of top output in host dumpPaul Eggleton2019-12-151-0/+1
| | | | | | | | | | | | | | | | | | If runqemu fails, there is some logic to run a set of commands to dump various bits of information that might help debug the issue (particularly in a busy situation such as on the autobuilder). One of those commands is "top -bn1", however top restricts the output to the width of the calling terminal, and for whatever reason this is a little restrictive when called from inside testimage, so set COLUMNS in the environment to a high value to fix it. (Another way is to use the -w option, but that is not supported by our default busybox configuration so it will then fail when this same list of commands is used on the target). (From OE-Core rev: 07da998f5aa6c3f5ffeee5150fc579e8a1051ba4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: ensure that host dump commands can be run properlyPaul Eggleton2019-12-151-1/+3
| | | | | | | | | | | | | | | | | If runqemu fails, there is some logic to run a set of commands to dump various bits of information that might help debug the issue (particularly in a busy situation such as on the autobuilder). However, when we try to run these we are inside the normal build environment which restricts commands to be run on the host to those specified in HOSTTOOLS. Since this isn't a place where host contamination is going to be a problem, override PATH to a reasonable default so that we run the actual host tools directly to avoid the issue. (Logically we would want to use the original PATH value here, but it is not easily accessible.) (From OE-Core rev: 3f6dcf67bccb4f0fc1a9a64e02bd0e2da620ad0e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revision3.1_M1Richard Purdie2019-12-121-1/+1
| | | | | | (From OE-Core rev: 0f04e81c797d5d337ece4e8638a6b71c75bc0a00) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-121-1/+1
| | | | | | (From OE-Core rev: 0980868fb1a315b2bb2ccd8d36873808056cb1ee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-111-1/+1
| | | | | | (From OE-Core rev: cb5e746a2398d70b14a14ada7cef82bfd5e80d0e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure mkdir happens before mktempRichard Purdie2019-12-111-3/+2
| | | | | | | | | | This avoids a directory not present error. Fix a comment typo whilst here. (From OE-Core rev: 1360d8d7d99b70a80c8cdbc1fc6d9e6752483139) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-111-1/+1
| | | | | | (From OE-Core rev: bf6ee2b39e2294f7f3719f7d373af9e0ec2979e9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure target sstate directory exists if unihash changesRichard Purdie2019-12-111-2/+2
| | | | | | | | | The previous patches meant the mkdir might no longer match the final target directory. Fix this. (From OE-Core rev: 0af4dae84099e8632a9ea6a4afdbea2f232bb170) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 76e84ce1815ff273647657eeafb5149d6016730b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure SSTATE_PKG is reloaded when handling siginfoRichard Purdie2019-12-101-1/+2
| | | | | | | | | STATE_PKG may have been changed by sstate_report_unihash so don't cache the variable's value. (From OE-Core rev: be29a25400c4ea285ab3f588c5831f00ba5d4f63) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 093a1971f2ae12e1f514598da984f268607e550b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bluez: update 5.50 -> 5.52"Richard Purdie2019-12-109-16/+982
| | | | | | | | | This reverts commit dad8cd50bcc4203a65d153dc2445502c1e728975. It is causing performance problems in ptest, taking hours (~18) to parse the ptest runner logs. Log output increased from ~4MB to ~65MB. Revert until we can deal with the performance issue. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 42719edc86ac2013280a34f1c58ca83726cec04a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Stop overwriting SSTATE_PKGRichard Purdie2019-12-101-4/+4
| | | | | | | | | | | | Its rather antisocial to overwrite SSTATE_PKG with an expanded form for the variable and it stops the value of BB_UNIHASH being changed when the package is written out. Instead of expanding the variable, append to it instead to avoid this rather hard to figure out behaviour and allow the siggen code to behave as expected. (From OE-Core rev: 62eca02024b4c44d618ab9bcf87a3166c886dadb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-101-1/+1
| | | | | | (From OE-Core rev: 85b7a3d5ec553ef71fa6060b99afbdccdc87dd37) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2019-12-091-1/+1
| | | | | | (From OE-Core rev: efc1945a95897539a491f9e833ba07e653fdb1d4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: Switch to NVD CVE JSON feed version 1.1Niko Mauno2019-12-092-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Switch to recently released version 1.1 of NVD CVE JSON feed, as in https://nvd.nist.gov/General/News/JSON-1-1-Vulnerability-Feed-Release it is mentioned that Due to changes required to support CVSS v3.1 scoring, the JSON vulnerability feeds must be modified. This will require the consumers of this data to update their internal processes. We will be providing the JSON 1.1 schema on the data feeds page and the information below to prepare for this transition. ... The JSON 1.1 data feeds will be available on September 9th, 2019. At that time the current JSON 1.0 data feeds will no longer available. This change was tested briefly by issuing 'bitbake core-image-minimal' with 'cve-check.bbclass' inherited via local.conf, and then comparing the content between the resulting two 'DEPLOY_DIR_IMAGE/core-image-minimal-qemux86.cve' files, which did not seem to contain any other change, except total of 167 entries like CVSS v3 BASE SCORE: 0.0 were replaced with similar 'CVSS v3 BASE SCORE:' entries which had scores that were greater than '0.0' (up to '9.8'). (From OE-Core rev: cc20e4d8ff2f3aa52a2658404af9a0ff358cc323) Signed-off-by: Niko Mauno <niko.mauno@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcap-ng: add missing Upstream-Status tagsRoss Burton2019-12-092-0/+2
| | | | | | | (From OE-Core rev: b45c967a8324c10642f2ef445f4c8c1a82947e1f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* texinfo: update to 6.7Alexander Kanavin2019-12-095-74/+49
| | | | | | | | | | | | | Drop 0001-Unset-need_charset_alias-when-building-for-musl.patch as the problematic code is gone. Rebase the other patches. License-Update: http links changed to https (From OE-Core rev: b234a4ed4d6a9c2e00f5fa38cf04867c7ada24a0) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* flex: Replace uninative loader pathJoshua Watt2019-12-091-0/+5
| | | | | | | | | | | | | | The Makefile used for flex-ptest can pick up the path to the uninative loader through BUILD_LDFLAGS. This includes the full path to the uninative loader, which is not reproducible. Replace it with /bin/false. It doesn't appear as if these native programs are used in the test suites and if there are likely to be other problems related to building them using the BUILD_* flags. (From OE-Core rev: 3cce2d1c36b0859186139d650fd50d2a56e91abd) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bash: Don't DEPEND on virtual/libc-localeAdrian Bunk2019-12-091-1/+0
| | | | | | | | | | For ptest only RDEPENDS is needed, and packaging glibc-locale slowed down builds with ptest disabled. (From OE-Core rev: 53f61ca73e69508bff6ea75da666d6873b5384f5) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/runtime_test: split systemd and sysvinit tests outArmin Kuster2019-12-091-35/+62
| | | | | | | | | | | | | This should help debug which part of this selftest is failing. We can not tell which outloop is failing so split the tests into systemd and sysvinit. [YOCTO #13650] (From OE-Core rev: 5f49ac73ca38ae711e093b35ae0feb5a0674198a) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.33.1Khem Raj2019-12-0932-1434/+719
| | | | | | | | | | Drop CVE patches which are already available on binutils-2_33-branch Forward port rest of the patches (From OE-Core rev: 7bcfce05045fb7e10456aa1f5301e70c178f20d7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot-fw-utils: Add capability of building from out-of-treeDaisuke Yamane2019-12-091-6/+6
| | | | | | | | | This patch also helps to build with EXTERNALSRC. (From OE-Core rev: e63dc57f0950dbfc594efe8570333a16baadf51a) Signed-off-by: Daisuke Yamane <yamane07ynct@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ghostscript: upgrade 9.27 -> 9.50Trevor Gamblin2019-12-094-581/+3
| | | | | | | | | | | | | Version 9.50 incorporates previously-backported fixes for CVE-2019-14811 and CVE-2019-14817. CVE: CVE-2019-14811 CVE: CVE-2019-14817 (From OE-Core rev: 8c626421840da9441be03587a57e9cf1ebd3d6f0) Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "libtirpc: create the symbol link for rpc header files"Peter Kjellerstedt2019-12-091-15/+1
| | | | | | | | | | | | | | | | | | This reverts commit 674596421320de08142e010fdd65ec6f0a0f34e9 and 9dc1aaed83f0627db65f387de0b1e51503ab07b1. The headers provided by libtirpc are not drop in replacements for the RPC header files previously provided by glibc, so do not install them as if they were. Additionally, they clash with the header files installed by glibc if an older version of glibc is used. Any problems related to the lack of the old header files from glibc should be addressed in the application/library that expects them. (From OE-Core rev: 8311e8b399fda66deee980dfd36068fafed2a2aa) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: update to 2.62.3Alexander Kanavin2019-12-093-22/+20
| | | | | | | (From OE-Core rev: 2800abbcbd6f3741ceb9ab29371753de1cbc02e6) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxcrypt: update to 4.4.10Alexander Kanavin2019-12-093-1/+2
| | | | | | | (From OE-Core rev: 548d9fefef024a2f8e323dade8456396f982f637) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxcrypt: restructure the recipes to allow auto-upgrading with devtoolAlexander Kanavin2019-12-093-34/+35
| | | | | | | (From OE-Core rev: f1bb43d0b9537ca63b88edfc3f5481dddf1f2a56) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* assimp: update to 5.0.0Alexander Kanavin2019-12-092-2/+1668
| | | | | | | (From OE-Core rev: de3117ef4ed05721a25d24bae91ab65cab3ca664) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-demos: update to latest revisionAlexander Kanavin2019-12-092-17/+14
| | | | | | | (From OE-Core rev: 2666f3978bd217303bb4306a14d9d88ab59dc697) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan: update to 1.1.126Alexander Kanavin2019-12-093-6/+7
| | | | | | | | | | | Disable assembly for vulkan-loader, as it tries to execute a target binary (previously it would fail to detect a working assembler and do the same fallback quietly). (From OE-Core rev: fe2db77803846faa29226b821aaa985e009ac3cc) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* orc: update to 0.4.31Alexander Kanavin2019-12-091-3/+7
| | | | | | | | | Switch to meson build system. (From OE-Core rev: 3abc02e38d818be54876c8354abbd518396067a9) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: Whitelist CVE-2019-0190Adrian Bunk2019-12-091-0/+4
| | | | | | | | | This is only a problem with older Apache versions. (From OE-Core rev: 492d43296b15514ec72dfb15f37c6d2ab1fbbae3) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Upgrade 243 -> 243.2Adrian Bunk2019-12-093-42/+2
| | | | | | | | | | | Bugfix-only changes on the 243 stable branch. Backported patch removed. (From OE-Core rev: 0406dd71964fca391b57f7bf43a7f37f6549fa15) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: rv32/rv64 target builds are not supported yetKhem Raj2019-12-091-0/+3
| | | | | | | (From OE-Core rev: c1efb1772cfae044969233fe9a394ef163d7bd51) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: Whitelist CVE-2017-17522 CVE-2017-18207 CVE-2015-5652Adrian Bunk2019-12-091-0/+10
| | | | | | | | | | One Windows-only CVE that cannot be fixed, and two CVEs where upstream agreement is that they are not vulnerabilities. (From OE-Core rev: 56d5b181f3b119f2bbd310dedd6d3b26e76f5944) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson.bbclass: Prevent meson from downloading wrapped projectsPeter Kjellerstedt2019-12-091-1/+2
| | | | | | | | | | | | | Meson has support for downloading subprojects using something called wraps. This interferes with bitbake's expectations of all downloads being done by the fetch task. To avoid this, tell meson to not download any wraps. Suggested-by: Mattias Jernberg <mattias.jernberg@axis.com> (From OE-Core rev: b547637ad84bad8f7fe27193bf636541f8588ae8) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-10-05 19:01:59 +0000