>
> int thp_read_string(const char *name, const char * const strings[])
> @@ -165,11 +140,7 @@ void thp_write_string(const char *name, const char *val)
> printf("%s: Pathname is too long\n", __func__);
> exit(EXIT_FAILURE);
> }
> -
> - if (!write_file(path, val, strlen(val) + 1)) {
> - perror(path);
> - exit(EXIT_FAILURE);
> - }
> + write_file(path, val, strlen(val) + 1);
Wondering what happens if a test like migration.c that uses
kselftest_harness.h ends up calling ksft_exit_fail_msg().
I assume the ksft_exit_fail* will simply set exit(KSFT_FAIL) and make
the __wait_for_test() helper happy.
Acked-by: David Hildenbrand (Arm) <[email protected]>
--
Cheers,
David
