Commit 453ebbefe2e5 for kernel

commit 453ebbefe2e504057cdcd0e422ba39ed8b99434f
Merge: b92f6e90cf05 5b598ba5f3bf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Oct 30 14:09:26 2026 -1000

    Merge tag 'ktest-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest

    Pull ktest updates from Steven Rostedt:

     - Sort configs before writing config file

       Currently the .config file is created from the perl hash array from
       reading the applied min-configs. The order is determined by how perl
       hashes the values. This causes the .config file to be created in
       different orders for each run, and the order may determine the final
       value of the .config file after it goes through a make oldconfig.

       Sort the values when creating the .config so that the result is the
       same for every run.

     - Add total test time to run output

       Have ktest display the total test time of running all the tests. This
       is useful to find issues in the build, install, boot or test run
       where things are hanging for longer than expected.

     - Update reading of the git output during bisect

       The ktest bisect is an automated way to run git bisect. Since there
       currently no easy way to know if the bisect found the bad commit (I'm
       talking with the git maintainers to fix this[1]), it parses the
       output for the line "is first bad commit". But a recent update to git
       has the output state "is the first 'bad' commit" which breaks ktest
       bisect.

       Have ktest handle both output strings.

       [1] https://lore.kernel.org/all/20261020141011.0015d172@gandalf.local.home/

    * tag 'ktest-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest:
      ktest: Accept quoted bad term in git bisect output
      ktest.pl: Add total test run time to output
      ktest: Sort config keys before writing config files