From: linuxtestproject.agent@gmail.com
To: Piotr Kubaj <piotr.kubaj@intel.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] high_freq_hwp_cap_cppc.c: new test
Date: Thu, 7 May 2026 09:38:40 +0000 [thread overview]
Message-ID: <20260507093840.3898-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260507072238.102543-2-piotr.kubaj@intel.com>
Hi Piotr,
On 2026-05-07, Piotr Kubaj wrote:
> high_freq_hwp_cap_cppc.c: new test
> + mismatch = SAFE_MALLOC(nproc, sizeof(int));
SAFE_MALLOC takes a single size argument. This will not compile.
Use SAFE_CALLOC(nproc, sizeof(int)) instead.
---
Note:
Our agent completed the review of the patch. The full review can be
found at: https://github.com/linux-test-project/ltp-agent/actions/runs/25487767963
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-07 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 7:22 [LTP] [PATCH v12] high_freq_hwp_cap_cppc.c: new test Piotr Kubaj
2026-05-07 7:29 ` Andrea Cervesato via ltp
2026-05-14 9:25 ` Kubaj, Piotr
2026-05-07 8:34 ` Andrea Cervesato via ltp
2026-05-07 9:38 ` linuxtestproject.agent [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-14 9:35 [LTP] [PATCH v13] " Piotr Kubaj
2026-05-14 11:58 ` [LTP] " linuxtestproject.agent
2026-05-06 12:56 [LTP] [PATCH v11] " Piotr Kubaj
2026-05-06 14:15 ` [LTP] " linuxtestproject.agent
2026-05-05 9:54 [LTP] [PATCH v10] " Piotr Kubaj
2026-05-05 17:54 ` [LTP] " linuxtestproject.agent
2026-05-04 10:17 [LTP] [PATCH v9] " Piotr Kubaj
2026-05-04 11:55 ` [LTP] " linuxtestproject.agent
2026-04-20 9:44 [LTP] [PATCH v7] " Piotr Kubaj
2026-04-20 10:53 ` [LTP] " linuxtestproject.agent
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=20260507093840.3898-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=piotr.kubaj@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.