Searched refs:regress (Results 1 – 7 of 7) sorted by relevance
| /linux-6.15/tools/testing/selftests/timers/ |
| H A D | freq-step.c | 111 static void regress(struct sample *samples, int n, double *intercept, in regress() function
173 regress(samples, SAMPLES, &intercept, &slope, &stddev1, &max1); in run_test()
180 regress(samples, SAMPLES / 2, &intercept, &slope, &stddev1, &max1); in run_test()
184 regress(samples + SAMPLES / 2, SAMPLES / 2, &intercept, &slope, in run_test()
|
| /linux-6.15/Documentation/driver-api/cxl/ |
| H A D | maturity-map.rst | 26 Note that this score can regress from one kernel release to the next
|
| /linux-6.15/Documentation/gpu/rfc/ |
| H A D | i915_scheduler.rst | 16 functional, no major coding style / layering errors, and not regress
|
| /linux-6.15/Documentation/process/ |
| H A D | handling-regressions.rst | 617 We do not regress, and we do not regress exactly because your are 100% wrong.
624 The whole point of "we do not regress" is so that people can upgrade
|
| /linux-6.15/Documentation/gpu/ |
| H A D | drm-uapi.rst | 579 core don't regress existing functionality. This test suite is called IGT and
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | f2fs.rst | 252 pass, but the performance will regress. "nobarrier" is
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | cgroup-v2.rst | 218 behavior that could regress existing setups, so it must be
|