All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [PATCH 0/2] power_management: cleanup
Date: Wed, 18 Mar 2026 14:44:53 +0100	[thread overview]
Message-ID: <20260318134453.GA19771@pevik> (raw)
In-Reply-To: <20260318132639.18818-1-pvorel@suse.cz>

Hi,

> Hi,

> I wanted to delete whole old testsuite (README mentions ancient kernel
> 2.6.29.4 etc) but because Intel folks contributed power management test
> [1] and CPUFREQ/CPUIDLE sysfs tests are probably valid and should be
> rewritten.

Other problem is that all x86_64 machines I debug have all
/sys/devices/system/cpu/cpu*/topology/physical_package_id
files only 0, therefore all runpwtests_exclusive0*.sh are skipped.

> Of course README itself is also outdated (some scripts has been removed
> and code put into the servers).

> [1] https://lore.kernel.org/ltp/20260318130250.68495-2-piotr.kubaj@intel.com/


> Petr Vorel (2):
>   runpwtests03.sh: Replace modprobe -l to lsmod
>   power_management: Remove runpwtests0[125].sh

>  runtest/power_management_tests                |  3 -
Given how old tests are is completely useless "_tests" suffix on the runtest
file. I know renaming runtest files is not practical (at least Cyril was against
in the past), but in this case I'd be for renaming it.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      parent reply	other threads:[~2026-03-18 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 13:26 [LTP] [PATCH 0/2] power_management: cleanup Petr Vorel
2026-03-18 13:26 ` [LTP] [PATCH 1/2] runpwtests03.sh: Replace modprobe -l to lsmod Petr Vorel
2026-03-26 13:41   ` Andrea Cervesato via ltp
2026-03-30  8:10     ` Petr Vorel
2026-03-18 13:26 ` [LTP] [PATCH 2/2] power_management: Remove runpwtests0[125].sh Petr Vorel
2026-03-26 13:33   ` Andrea Cervesato via ltp
2026-03-30  8:13     ` Petr Vorel
2026-03-18 13:44 ` 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=20260318134453.GA19771@pevik \
    --to=pvorel@suse.cz \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=ltp@lists.linux.it \
    /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.