All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Frank Ranner <frank.ranner@intel.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] testcases/kernel/crypto/crypto_user02.c: fix hmac candidate probing
Date: Thu, 13 Aug 2026 15:00:51 +0000	[thread overview]
Message-ID: <20260813150051.8847-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260813140609.57520-1-frank.ranner@intel.com>

Hi Frank,

On Aug 13, 2026, Frank Ranner wrote:
> testcases/kernel/crypto/crypto_user02.c: fix hmac candidate probing

> Fixes: a4be708b4 ("testcases/kernel/crypto/crypto_user02.c: try non-generic hmac names first")

Medium: Could this use c05a44cf1 instead? The referenced a4be708b4 does not
resolve to a commit in the local LTP history, while c05a44cf1 has the quoted
subject.

> +		/* find out which driver actually satisfies this name */
> +		memset(&report, 0, sizeof(report));
> +		strcpy(report.cru_name, ALGORITHM_CANDIDATES[i]);
> +		if (tst_crypto_get_alg(ctx, &report) != 0)

Low: Could this comment be removed? It only restates the
tst_crypto_get_alg() call, while LTP comments should explain why rather than
narrate the code.

Verdict - Needs revision

---
Note:

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

  reply	other threads:[~2026-08-13 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 14:06 [LTP] [PATCH ltp] testcases/kernel/crypto/crypto_user02.c: fix hmac candidate probing Frank Ranner
2026-08-13 15:00 ` linuxtestproject.agent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-13 15:24 [LTP] [PATCH v2 " Frank Ranner
2026-08-13 16:04 ` [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=20260813150051.8847-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=frank.ranner@intel.com \
    --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.