public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: "Kubaj, Piotr" <piotr.kubaj@intel.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"Ossowski, Tomasz" <tomasz.ossowski@intel.com>,
	"Dubel, Helena Anna" <helena.anna.dubel@intel.com>,
	"Niestepski, Daniel" <daniel.niestepski@intel.com>,
	"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2] thermal: add new test group
Date: Fri, 23 Jan 2026 20:48:36 +0100	[thread overview]
Message-ID: <20260123194836.GA435072@pevik> (raw)
In-Reply-To: <4366caa2f3055b446e421278d314265c1c3b32ad.camel@intel.com>

Hi Piotr,

...
> Hi,

> I tried:
> SAFE_SSCANF(line, " TRM:%sThermal event interrupts", buffer);

I'm sorry, you wrote that, but I did not get that the line is based on number of
CPU core (I meant scanning into integer variables).

> But it's the same as before, only the first number ends up in the
> buffer. Still, even if I managed to put them all into buffer, I would
> still need to later divide them into individual elements of
> interrupt_array and strtok seems fit for that.

I'm usually trying to avoid using strtok(), but whatever.

Kind regards,
Petr

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

  reply	other threads:[~2026-01-23 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 14:46 [LTP] [PATCH v2] thermal: add new test group Piotr Kubaj
2026-01-20 19:38 ` Petr Vorel
2026-01-21 11:55   ` Kubaj, Piotr
2026-01-21 23:06     ` Petr Vorel
2026-01-22 14:27     ` Petr Vorel
2026-01-23 12:37       ` Kubaj, Piotr
2026-01-23 19:48         ` Petr Vorel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-14 18:01 Piotr Kubaj
2025-11-18 18:18 ` Cyril Hrubis
2025-11-19  9:35   ` Cyril Hrubis

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=20260123194836.GA435072@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox