Linux Power Management development
 help / color / mirror / Atom feed
From: Ali Ahmet Memis <ali@iusegentoo.com>
To: Shuah <shuah@kernel.org>, Thomas Renninger <trenn@suse.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	"John B . Wyatt IV" <jwyatt@redhat.com>,
	John Kacur <jkacur@redhat.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpupower: Avoid uninitialized reads in topology sorting
Date: Mon,  3 Aug 2026 16:36:18 +0000	[thread overview]
Message-ID: <20260803163620.104223-1-ali@iusegentoo.com> (raw)
In-Reply-To: <c746110c-6ac4-4500-a4f0-491a06838173@kernel.org>

On Mon, Aug 03, 2026 at 10:29:15AM -0600, Shuah wrote:
> Sorry I am not taking this patch.
>
> Please note that build test just verifies that the code build which
> fall way short of testing the changed code.

First, sorry about the duplicates. The mail provider I was using at the
time rewrote the Message-ID and delivered the same patch several times, so
it hit the list as a handful of separate threads. That was not me resending
it. I have moved off that provider and everything since August 1 goes out
with a stable Message-ID from git send-email.

The valgrind run was in the notes under the scissors, not just a build: a
two-CPU mock where CPU1's topology reads fail, uninitialized reads in
__compare_core_cpu_list() before the patch and none after. If there is
testing you would want beyond that, tell me what would satisfy you and I
will do it. Otherwise I am fine dropping this.

  reply	other threads:[~2026-08-03 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7fa98ba5-6790-48b4-b102-c1193685822f@smtp-relay.sendinblue.com>
2026-08-03 16:29 ` [PATCH] cpupower: Avoid uninitialized reads in topology sorting Shuah
2026-08-03 16:36   ` Ali Ahmet Memis [this message]
2026-08-03 17:37     ` Shuah
2026-07-30  2:07 Ali Ahmet Memis

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=20260803163620.104223-1-ali@iusegentoo.com \
    --to=ali@iusegentoo.com \
    --cc=jkacur@redhat.com \
    --cc=jwyatt@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=trenn@suse.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