From: Petr Vorel <pvorel@suse.cz>
To: Piotr Kubaj <piotr.kubaj@intel.com>
Cc: helena.anna.dubel@intel.com, tomasz.ossowski@intel.com,
rafael.j.wysocki@intel.com, ltp@lists.linux.it,
daniel.niestepski@intel.com
Subject: Re: [LTP] [PATCH v10] thermal: add new test group
Date: Mon, 2 Mar 2026 14:45:01 +0100 [thread overview]
Message-ID: <20260302134501.GA280343@pevik> (raw)
In-Reply-To: <20260226143134.138506-3-piotr.kubaj@intel.com>
Hi Piotr, all,
I like the runtime drastically speedup :).
...
> +static void cleanup(void)
> +{
> + if (x86_pkg_temp_tz_found)
> + SAFE_FILE_PRINTF(trip_path, "%d", trip);
We discussed EINVAL error on a first run in [1]
thermal_interrupt_events.c:178: TWARN: Failed to close FILE '/sys/class/thermal/thermal_zone1/trip_point_1_temp': EINVAL (22)
This happens in safe_file_vprintf(), just TBROK is converted to TWARN due being
in cleanup(). I wonder if separate test for this would be useful.
You pointed a kernel fix [2] bug git hash changed (now cgit shows Bad commit
"reference: 39b1bd1613b8f73994f654988ad75a72b633f5e2"). Do you know the new hash
of the fix? Maybe putting the hash info in the test would be useful
.tags = (const struct tst_tag[]) {
{"linux-git", "..."}, // hash of the fix
{}
nit (we discussed it in the past): when x86_pkg_temp_tz_found is bool, instead
of using 1:
x86_pkg_temp_tz_found = 1;
would be cleaner to use true.
Otherwise LGTM now.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
[1] https://lore.kernel.org/ltp/20260121230639.GA10001@pevik/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/patch/?id=39b1bd1613b8f73994f654988ad75a72b633f5e2
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-03-02 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 14:31 [LTP] [PATCH v10] thermal: add new test group Piotr Kubaj
2026-03-02 13:45 ` Petr Vorel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260302134501.GA280343@pevik \
--to=pvorel@suse.cz \
--cc=daniel.niestepski@intel.com \
--cc=helena.anna.dubel@intel.com \
--cc=ltp@lists.linux.it \
--cc=piotr.kubaj@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tomasz.ossowski@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.