diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2024-03-18 15:27:03 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2024-03-18 15:27:03 -0700 |
| commit | 65b64246f28bee13f9c15e4f0847fd6cca39ada3 (patch) | |
| tree | e4be815689faf1c90b04c397a3720ecc086e3099 /tools/perf/util/pmu.c | |
| parent | ad584d73a22b2f6e6b4c928956fdece5c44cdb3e (diff) | |
| parent | 07283c1873a4d0eaa0e822536881bfdaea853910 (diff) | |
| download | linux-stable-65b64246f28bee13f9c15e4f0847fd6cca39ada3.tar.gz linux-stable-65b64246f28bee13f9c15e4f0847fd6cca39ada3.tar.bz2 linux-stable-65b64246f28bee13f9c15e4f0847fd6cca39ada3.zip | |
Merge tag 'ktest-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest
Pull ktest updates from Steven Rostedt:
- Allow variables to contain variables. This makes the shell commands
have a bit more flexibility to reuse existing variables.
- Have make_warnings_file in build-only mode require limited variables
The make_warnings_file test will create a file with all existing
warnings (which can be used to compare against in builds with new
commits). Add it to the build-only list that doesn't require other
variables (like how to reset a machine), as the make_warnings_file
makes the most sense on build only tests.
* tag 'ktest-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest:
ktest: force $buildonly = 1 for 'make_warnings_file' test type
ktest.pl: Process variables within variables
Diffstat (limited to 'tools/perf/util/pmu.c')
0 files changed, 0 insertions, 0 deletions