Files
linux/drivers/gpu/drm/xe
Linus Torvalds 30bbcb4470 Merge tag 'linux_kselftest-kunit-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
Pull kunit updates from Shuah Khan:

 - New parameterized test features

   KUnit parameterized tests supported two primary methods for getting
   parameters:

    - Defining custom logic within a generate_params() function.

    - Using the KUNIT_ARRAY_PARAM() and KUNIT_ARRAY_PARAM_DESC() macros
      with a pre-defined static array and passing the created
      *_gen_params() to KUNIT_CASE_PARAM().

   These methods present limitations when dealing with dynamically
   generated parameter arrays, or in scenarios where populating
   parameters sequentially via generate_params() is inefficient or
   overly complex.

   These limitations are fixed with a parameterized test method

 - Fix issues in kunit build artifacts cleanup

 - Fix parsing skipped test problem in kselftest framework

 - Enable PCI on UML without triggering WARN()

 - a few other fixes and adds support for new configs such as MIPS

* tag 'linux_kselftest-kunit-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
  kunit: Extend kconfig help text for KUNIT_UML_PCI
  rust: kunit: allow `cfg` on `test`s
  kunit: qemu_configs: Add MIPS configurations
  kunit: Enable PCI on UML without triggering WARN()
  Documentation: kunit: Document new parameterized test features
  kunit: Add example parameterized test with direct dynamic parameter array setup
  kunit: Add example parameterized test with shared resource management using the Resource API
  kunit: Enable direct registration of parameter arrays to a KUnit test
  kunit: Pass parameterized test context to generate_params()
  kunit: Introduce param_init/exit for parameterized test context management
  kunit: Add parent kunit for parameterized test context
  kunit: tool: Accept --raw_output=full as an alias of 'all'
  kunit: tool: Parse skipped tests from kselftest.h
  kunit: Always descend into kunit directory during build
2025-10-01 19:15:11 -07:00
..
2025-09-17 20:23:47 -04:00
2025-08-14 10:30:53 -04:00
2024-05-09 21:28:25 +02:00
2025-07-14 13:20:02 -07:00
2025-01-09 17:58:09 +01:00
2025-06-27 14:52:31 -07:00
2025-06-02 11:00:46 -07:00
2025-06-27 14:52:31 -07:00
2025-07-01 13:58:50 -07:00
2025-06-27 14:52:31 -07:00
2025-06-27 14:52:31 -07:00
2025-03-25 20:51:29 -07:00
2025-01-14 07:02:49 -08:00
2024-11-15 15:59:51 -08:00
2025-09-17 20:23:47 -04:00
2024-05-13 21:36:50 +02:00
2025-06-27 14:52:31 -07:00
2025-07-01 13:55:19 -07:00
2025-07-01 13:55:19 -07:00
2025-09-17 20:23:47 -04:00
2025-06-27 14:52:31 -07:00
2024-05-22 12:03:55 +02:00
2025-09-15 13:11:40 -04:00
2025-07-14 13:40:17 -07:00
2024-09-19 10:15:40 +02:00
2024-05-07 12:03:49 +02:00
2025-08-14 10:30:53 -04:00
2025-01-27 08:54:06 -08:00
2025-02-03 11:51:26 -08:00
2024-05-13 21:36:52 +02:00
2025-07-14 07:55:18 -07:00
2025-07-14 07:55:18 -07:00
2025-01-19 00:12:02 +01:00
2025-06-27 14:52:31 -07:00
2025-07-28 10:22:28 -04:00
2025-01-17 00:01:58 +05:30
2025-04-10 15:50:01 -07:00