Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: priyama2 <priyama2@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] testcases/nvme: Add NVMe device discovery and identification test
Date: Wed, 29 Apr 2026 07:33:13 +0000	[thread overview]
Message-ID: <20260429073313.4011-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260430154852.896072-1-priyama2@linux.ibm.com>

Hi Priya,

On Thu, 30 Apr 2026 15:48:52 +0000, priyama2 wrote:
> testcases/nvme: Add NVMe device discovery and identification test
>
> This test verifies NVMe device discovery and identification by:
> - Detecting NVMe controllers in /dev
> [...]

The commit body describes what the test does but not why it is needed —
what coverage gap does this fill? Also, "Changes in v2:" belongs in the
cover letter, not the commit body; strip it before sending.

> +++ b/testcases/kernel/device-drivers/nvme/nvme01
> new file mode 100755
>  Bin 0 -> 995536 bytes

Do not commit compiled binaries. Remove nvme01 from the patch and add a
.gitignore in the test directory listing it.

> + * Copyright (c) 2024 IBM Corporation

This file is new and added in 2026; use the current year.

> +static int nvme_device_found;
> +static char nvme_dev_name[256];

These statics are set in case 0 of run() but never cleared. With -i,
stale state from a prior iteration persists into subsequent ones. Reset
them at the top of run().

> +	.needs_root = 1,

No operation in this test requires root. All reads from /dev and sysfs
are accessible to unprivileged users. Drop needs_root.

The patch is also missing a runtest entry (e.g. in runtest/drivers) and
a .gitignore entry for the nvme01 binary.

---
Note:

Our agent completed the review of the patch.

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-04-29  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260430154852.896072-1-priyama2@linux.ibm.com>
2026-04-29  7:33 ` linuxtestproject.agent [this message]
2026-04-29 10:51 [LTP] [PATCH] testcases/nvme: Add NVMe device discovery and identification test priyama2
2026-04-28  2:58 ` [LTP] " linuxtestproject.agent
  -- strict thread matches above, loose matches on Subject: below --
2026-04-30 15:52 [LTP] [PATCH v2] " priyama2
2026-04-29  7:33 ` [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=20260429073313.4011-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=priyama2@linux.ibm.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