Add a section on providing global level configuration from the
layer.conf file. Since this file is parsed at an earlier stage in the
parsing process, it's not possible to combine bb.utils.contains and
{DISTRO,MACHINE}_FEATURES to conditionally set some configurations.
This patch documents:
- First that this file can be used for providing such configuration.
- Then demonstrate how to conditionally provide them, using a technique
that is currently used in meta-virtualization
(https://git.yoctoproject.org/meta-virtualization/tree/conf/layer.conf#n50).
Fixes [YOCTO #12688].
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
(From yocto-docs rev: cc3fa1b0e51377f4e03eaa1ca60c2f2ee0cd917e)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To make references to the bitbake repo, add an extlink for it and use it
in the docs with ":bitbake_git:`lib/bb/utils.py </tree/lib/bb/utils.py>`".
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
(From yocto-docs rev: 989f966e1c2b8eec100fc448be3ba09cf358ba26)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Placeholder files for release 5.2 (Walnascar): migration guide and
release notes.
Define two substitutions |yocto-ver| and |yocto-codename| to avoid
mistakes in the document. Note that anchors cannot contain these so
add a note on that in a comment.
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
(From yocto-docs rev: f13492dc9474b7e22d01ab1bec2da074e972965d)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Don't hardcode matchbox-terminal, but use the alternative.
(From OE-Core rev: 0f04855243cb4a0bc4a60d7fb6bf47eef29043cf)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Don't hardcode matchbox-terminal, but use the alternative.
(From OE-Core rev: 3066d201633245ff53683ee12810977f25dde148)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of using rxvt as the fallback terminal use x-terminal-emulator.
Also add a recommends on something providing that name, as previously
it tried to use rxvt but that wasn't necessarily present.
(From OE-Core rev: f6ab4ab7cf16a49a5824112e573ba27c132bf3aa)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of depending on matchbox-terminal explicitly, just depend on
the virtual name.
core-image-x11 then uses rxvt instead of matchbox-terminal, as that is
the default, removing the entire GTK+ stack from the image.
core-image-sato and friends are unchanged as the sato packagegroup pulls
in matchbox-terminal explicitly, so rxvt isn't needed.
(From OE-Core rev: e3820f60412497d759c7b0715bdf303f787c1432)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We have multiple recipes in core that RPROVIDE virtual-x-terminal-emulator,
so we should pick one to be the default for deterministic builds.
Pick rxvt, as it's the lightest. Sato can depend on matchbox-terminal
explicitly and rxvt will not be added.
(From OE-Core rev: 0c362390127fa30f6932558ebcd9cbe1e21e8467)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a RPROVIDES for virtual-x-terminal-emulator, so that:
- Packages can RDEPEND on virtual-x-terminal-emulator and know that they
have installed a terminal
- The x-terminal-emulator binary will (via alternatives) run a terminal
We don't bother with PROVIDES because nobody needs to DEPEND on a terminal,
the entire point of this is that the actual binary is interchangable.
(From OE-Core rev: e1261ed6c3af803371f7a53eff18015828947d30)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
rxvt is a classic X11 application, so add the feature check so it doesn't
get pulled into world builds without x11.
(From OE-Core rev: 3530b250e32fb0f164899d60019633d2ecf8ef67)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The point of the virtual-x-terminal-emulator alternative was to provide
a single binary that executes whatever terminal has been installed. This
is a runtime choice, so should be RPROVIDES.
This doesn't need built-time PROVIDES, which actively get in the way
when multiple recipes are being built with the same PROVIDES.
(From OE-Core rev: 841df9b9eba52b65456650bfd9f667d77072d6f8)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch "Set relative to top_builddir path in Makefile to access"
sets the default path of `test-driver` to
`$(top_builddir)/$(config_aux_dir)` instead of the normal
`$(top_srcdir)/$(config_aux_dir)`.
This breaks `check test` for Automake projects in generated images,
and probably other places like SDKs.
A typical error would be
/bin/sh: ./build-aux/test-driver: No such file or directory
Removing the patch makes such checks complete successfully.
Fixes [YOCTO #15635]
(From OE-Core rev: d21dbafda92263d3e30a5b7d84dd9bb02f855610)
Signed-off-by: Ola x Nilsson <olani@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a sed substitution for ${PTEST_PATH}/tests/Makefile that
transforms
TEST_LOG_DRIVER = $(SHELL) $(top_srcdir)/build-aux/test-driver
to
TEST_LOG_DRIVER = $(SHELL) $(top_builddir)/build-aux/test-driver
which is where the test-driver script can be found when installed.
There used to be an oe-core automake patch to do this, but it
broke non-ptest use of automake.
Relates to [YOCTO #15635]
(From OE-Core rev: cfa585b93192222904ca99b7533d21726089b11c)
Signed-off-by: Ola x Nilsson <olani@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a sed substitution for ${PTEST_PATH}/tests/Makefile that transforms
SH_LOG_DRIVER = $(SHELL) $(top_srcdir)/build-aux/test-driver
to
SH_LOG_DRIVER = $(SHELL) $(top_builddir)/build-aux/test-driver
which is where the test-driver script can be found when installed.
There used to be an oe-core automake patch to do this, but it
broke non-ptest use of automake.
Relates to [YOCTO #15635]
(From OE-Core rev: e1274fd52c7d7a41af60f5f19ba2163dba3d973f)
Signed-off-by: Ola x Nilsson <olani@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a sed substitution for ${PTEST_PATH}/Makefile that transforms
SH_LOG_DRIVER = $(SHELL) $(top_srcdir)/build-aux/test-driver
PL_LOG_DRIVER = $(SHELL) $(top_srcdir)/build-aux/test-driver
to
SH_LOG_DRIVER = $(SHELL) $(top_builddir)/build-aux/test-driver
PL_LOG_DRIVER = $(SHELL) $(top_builddir)/build-aux/test-driver
which is where the test-driver script can be found when installed.
There used to be an oe-core automake patch to do this, but it
broke non-ptest use of automake.
Relates to [YOCTO #15635]
(From OE-Core rev: 2f7c365e97aa2205187e0ea426e17228cf91ad83)
Signed-off-by: Ola x Nilsson <olani@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a sed substitution for ${PTEST_PATH}/Makefile that transforms
TEST_LOG_DRIVER = $(SHELL) $(top_srcdir)/build-aux/test-driver
to
TEST_LOG_DRIVER = $(SHELL) $(top_builddir)/build-aux/test-driver
which is where the test-driver script can be found when installed.
There used to be an oe-core automake patch to do this, but it
broke non-ptest use of automake.
Relates to [YOCTO #15635]
(From OE-Core rev: 289db96b441e01c4ba1bbcd76fcf52b3258f2613)
Signed-off-by: Ola x Nilsson <olani@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a sed substitution for ${PTEST_PATH}/Makefile that transforms
TEST_LOG_DRIVER = $(SHELL) $(top_srcdir)/build-aux/test-driver
to
TEST_LOG_DRIVER = $(SHELL) $(top_builddir)/build-aux/test-driver
which is where the test-driver script can be found when installed.
There used to be an oe-core automake patch to do this, but it
broke non-ptest use of automake.
Relates to [YOCTO #15635]
(From OE-Core rev: a951447ca3b51f77272381c8e0c5837671fabbbd)
Signed-off-by: Ola x Nilsson <olani@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Specifically when using useradd-staticids this fails without
creating a ptest user entry.
ERROR: Nothing PROVIDES 'ptest-runner' ptest-runner was skipped: Recipe ptest-runner, package ptest-runner: system username "ptest" does not have a static ID defined. Add ptest to one of these files: .../passwd
...
...
Missing or unbuildable dependency chain was: ['my-image-sdk', 'packagegroup-core-sdk', 'quilt', 'ptest-runner']
This is seen when ptest is not even enabled. We fix this by
making a conditional dependency on the ptest-runner.
(From OE-Core rev: f4cc8bfe9c7d936ed36023f955d34f57676597d6)
Signed-off-by: Awais B <awais.belal@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Below commit on binutils-2.43.1 stable branch are updated.
b82e2250574 Automatic date update in version.in
280374309b1 PR32300, --dependency-file: link dependencies are not all collected
263e116833e s390: Add arch15 instructions
645da6d426e s390: Relax risbg[n]z, risb{h|l}gz, {rns|ros|rxs}bgt operand constraints
7f7047a9c6c s390: Simplify (dis)assembly of insn operands with const bits
e7592364504 s390: Align opcodes to lower-case
d6ab1d2efdc s390: Document syntax to omit base register operand
c40337b1784 LoongArch: Add elfNN_loongarch_mkobject to initialize LoongArch tdata
95ed7cf1be2 segv in bfd_elf_get_str_section
0a71d78f6a6 ld: Don't explicitly add .note.gnu.build-id in elf.sc
ad2ce1e6457 x86: Turn PLT32 to PC32 only for PC-relative relocations
238493e7f09 x86-64: Disable PIE on PR gas/32189 test
68d5dbd315d x86-64: Never make R_X86_64_GOT64 section relative
d77d08180d1 x86/APX: Don't promote AVX/AVX2 instructions out of APX spec
f307db3d8b7 bfd: Pass true to ld_plugin_object_p
cd3e2b58f2c PR32109, aborting at bfd/bfd.c:1236 in int _bfd_doprnt
2d37b890e56 lto: Add a test for PR ld/32083
d16a1893c44 ld: Add an LTO test for common symbol override
e4cfe6dab3e Re-enable development changes on the 2_43 branch
Testing was done and there were no regressions found
(From OE-Core rev: 4950a2d67a85b3f4a643a46fdc54d348abce5ed6)
Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We have a challenge on the autobuilder where test results from both OE-Core
and poky are being mixed together during result storage which is confusing the
data. Add a way to filter to specific revisions as the least worst way to fix
the various issues this is causing.
(From OE-Core rev: 3f276a0dc65341668788853be2cf27ab6aa12b13)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These INSANE_SKIPs are specific to cython and unrelated to mesonpy, so
remove them. The new cython.bbclass should resolve the cause.
(From OE-Core rev: abe08a3238d162a1bdbc68172307eb3eb127bbb1)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Change recipes that depend on python3-cython-native to inherit cython
instead.
(From OE-Core rev: 8217b61c3838d4a43b63b78c5121d657f52b4b2b)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Recipes that use Cython typically also do some bespoke fixup. Add a
class to centralise the logic:
- Set CYTHON_PREFIX_MAP to stop build paths appearing in generated
objects
- Strip "Cython Metadata" blocks from generated code that ends up in the
-src package
(From OE-Core rev: 9752da112b618362d2fe1b61c8939b8410e98553)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Cython generates C source code that contains mentions to the original
.py files, which results in build paths being embedded inside the
binaries.
Implement prefix remapping to change these build paths to point at the
target debug directory, so that we don't leak build paths and have
reproducible builds.
This patch is currently not submitted upstream, but will be shortly and
I expect it to evolve before being merged.
(From OE-Core rev: cdbe8ef6b744f8e485c4bc77897ad545457ea51e)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are the following error when building doc/examples/cmake-multiple-shared-libraries:
ld: warning: liblttng-ust-common.so.1, needed by lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link)
ld: warning: liblttng-ust-tracepoint.so.1, needed by lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link)
ld: warning: liblttng-ust-common.so.1, needed by lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link)
ld: warning: liblttng-ust-tracepoint.so.1, needed by lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link)
ld: lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so: undefined reference to `lttng_ust_common_alloc_tls'
ld: lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so: undefined reference to `lttng_ust_urcu_after_fork_parent'
ld: lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so: undefined reference to `lttng_ust_urcu_after_fork_child'
ld: lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so: undefined reference to `lttng_ust_urcu_after_fork_parent'
ld: lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so: undefined reference to `lttng_ust_tp_probe_unregister_queue_release'
ld: lttng-ust/2.13.8/build/src/lib/lttng-ust/.libs/liblttng-ust.so: undefined reference to `lttng_ust_cancelstate_disable_pop'
collect2: error: ld returned 1 exit status
This change set removes the old patch file 0001-Makefile.am-update-rpath-link.patch,
adds a new patch file 0001-Fix-Build-examples-when-rpath-is-stripped-from-in-bu.patch.
(From OE-Core rev: 89394da1cbe98652e1d0bd59c762ff7da2d6a113)
Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit adds a patch to increase the timeout in the process-sigpipe
rust selftest to prevent occasional failures under heavy server load.
The patch aims to reduce the likelihood of false negatives when the test
environment is overloaded.
Patch file:
* oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
Fixes [YOCTO #15625]
(From OE-Core rev: 12c85933e2150ba78a8a914787e400c95c5cf585)
Signed-off-by: Peter Tatrai <peter.tatrai.ext@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We had previously excluded this test case due to failure in earlier versions.
However, with the latest version of Rust, this test case is passing.
As a result, we have removed it from the exclude list and added back into
the test suite for execution.
The rust-1.79 has been successfully tested with the current test inclusion.
(From OE-Core rev: a33edee3efe67f81229496e03a098454dc7df051)
Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The script does not work if the connman service is already stopped.
The start-stop-daemon checks for the existence of a specified process.
If such a process exists, start-stop-daemon sends it the signal specified
by --signal, and exits with error status 0. If such a process does
not exist, start-stop-daemon exits with error status 1 (0 if --oknodo is specified).
The script uses set -e so we need to add --oknodo option to stop
(From OE-Core rev: b1c1b67166049181136d5eb68740f3bf98bf670d)
Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The correct meson flag for the documentation is 'documentation'.
(From OE-Core rev: 8dc084abe583077e5d357c7d3eaf3a0ad0e6b2b0)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A small dependency allows the 1.3MB pci.ids file to be compressed down
to 300K.
(From OE-Core rev: a254c976eb77dc9d548dc145dab182d341e3d8f9)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This recipe once included the xorg common .inc file but had to reset
several variables. It no longer includes that file but there's a lot of
cruft to remove: the LICENSE being "MIT & MIT" and the features_check
class not checking for any features, specifically.
(From OE-Core rev: 2321b806b3cd833f2b8b1672f699bfca55874fb3)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The correct meson flag for the documentation is 'documentation'.
(From OE-Core rev: f754bce3de22cd2c9645b3599fef13503c464200)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We can't build documentation when doing a cross build, so disable it
explicitly to be clear.
(From OE-Core rev: 2706062d3a711ff0b2c03bee40b908ad329ebd6d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We can't build this combination right now because of a circular dependency,
but it's good to make it explicit.
(From OE-Core rev: 736be249c56fd9a603dbb8ece77612928bb25ce9)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
true/false for these options is deprecated, use enabled/disabled.
(From OE-Core rev: 9f3fbfb04d2a6e2d0dab63be0f04a539c4a803ed)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These are disabled out of the box but only because the dependencies are
not present. Explicitly disable them to be clear.
(From OE-Core rev: 6efa5d5ae086f7178b3f7516803f24c78274bba1)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If Unified Kernel Image was enabled via IMAGE_CLASSES, then
target should also boot the same uki at runtime.
(From OE-Core rev: 2ae651c869a19fd24b5a915451c1f99e1d7b32f0)
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add more explanatory comments, including when we can drop the patch.
(From OE-Core rev: 15091ef668b544ceb881f8179c0c25c97afd3f5f)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Enable verbose tests so that the output from the failing test is logged.
(From OE-Core rev: 2e031a41a3c8da591755f39898ba063e39d79aaa)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
arm64 needs some new files to regenerate the build environment
in 6.12+.
This is due to upstream commits:
commit e632bca07c8eef1de9dc50f4e4066c56e9d68b07
Author: Arnd Bergmann <arnd@arndb.de>
Date: Thu Jul 4 14:33:34 2024 +0200
arm64: generate 64-bit syscall.tbl
Change the asm/unistd.h header for arm64 to no longer include
asm-generic/unistd.h itself, but instead generate both the asm/unistd.h
contents and the list of entry points using the syscall.tbl scripts that
we use on most other architectures.
Once his is done for the remaining architectures, the generic unistd.h
header can be removed and the generated tbl file put in its place.
The Makefile changes are more complex than they should be, I need
a little help to improve those. Ideally this should be done in an
architecture-independent way as well.
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
and:
commit 712676ea2bb3882a852bcf49862c4247317fc9b2
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Tue Sep 3 12:09:17 2024 +0000
arm64: vDSO: Wire up getrandom() vDSO implementation
Hook up the generic vDSO implementation to the aarch64 vDSO data page.
The _vdso_rng_data required data is placed within the _vdso_data vvar
page, by using a offset larger than the vdso_data.
The vDSO function requires a ChaCha20 implementation that does not write
to the stack, and that can do an entire ChaCha20 permutation. The one
provided uses NEON on the permute operation, with a fallback to the
syscall for chips that do not support AdvSIMD.
This also passes the vdso_test_chacha test along with
vdso_test_getrandom. The vdso_test_getrandom bench-single result on
Neoverse-N1 shows:
vdso: 25000000 times in 0.783884250 seconds
libc: 25000000 times in 8.780275399 seconds
syscall: 25000000 times in 8.786581518 seconds
A small fixup to arch/arm64/include/asm/mman.h was required to avoid
pulling kernel code into the vDSO, similar to what's already done in
arch/arm64/include/asm/rwonce.h.
Signed-off-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Acked-by: Will Deacon <will@kernel.org>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
(From OE-Core rev: b3c24a31c29aa74a9d63a0ea0bcaccca73db870b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* the idea was to reuse the same function as I've noticed that the
QA check which was added to insane.bbclass in:
https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a
is in some cases more strcit than scripts/contrib/patchreview.py
To be honest I wasn't aware of scripts/contrib/patchreview.py
existence when I've asked about moving check_upstream_status()
to oe.qa in order to write standalone script just like
patchreview.py
* I've sent this long time ago:
https://lists.openembedded.org/g/openembedded-core/message/177207
but didn't like the sys.path.append to find oe.qa much or the
duplicated path to .patch file in the output, then I've forgot about
it until today in https://github.com/OE4T/meta-tegra/pull/1749
where checklayer found one more issue, which I haven't noticed
with patchreview.py before (because I've accidentally used a version
without this change). It's not perfect, but at least it will be
consistent with checklayer and patch-status QA check.
(From OE-Core rev: f291c08ea6a95638c3ad1f70434678bd5e374195)
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
