From: Daniel Wagner <wagi@kernel.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Chaitanya Kulkarni <kch@nvidia.com>,
linux-block@vger.kernel.org, Daniel Wagner <wagi@kernel.org>
Subject: [PATCH blktests v2 1/4] common/nvme: add debug nvmet path variable
Date: Tue, 08 Apr 2025 18:25:57 +0200 [thread overview]
Message-ID: <20250408-test-target-v2-1-e9e2512586f8@kernel.org> (raw)
In-Reply-To: <20250408-test-target-v2-0-e9e2512586f8@kernel.org>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Daniel Wagner <wagi@kernel.org>
---
common/nvme | 2 ++
1 file changed, 2 insertions(+)
diff --git a/common/nvme b/common/nvme
index 3761329d39e3763136f60a4751ad15de347f6e9b..04b49c2c1f9edc6de516398b537502fc30a92969 100644
--- a/common/nvme
+++ b/common/nvme
@@ -26,6 +26,8 @@ nvmet_blkdev_type=${nvmet_blkdev_type:-"device"}
NVMET_BLKDEV_TYPES=${NVMET_BLKDEV_TYPES:-"device file"}
nvme_target_control="${NVME_TARGET_CONTROL:-}"
NVMET_CFS="/sys/kernel/config/nvmet/"
+# shellcheck disable=SC2034
+NVMET_DFS="/sys/kernel/debug/nvmet/"
nvme_trtype=${nvme_trtype:-}
nvme_adrfam=${nvme_adrfam:-}
--
2.49.0
next prev parent reply other threads:[~2025-04-08 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 16:25 [PATCH blktests v2 0/4] blktests: add target test cases Daniel Wagner
2025-04-08 16:25 ` Daniel Wagner [this message]
2025-04-08 16:25 ` [PATCH blktests v2 2/4] common/nvme: move nvmf_wait_for_state to common code Daniel Wagner
2025-04-08 16:25 ` [PATCH blktests v2 3/4] nvme/060: add test nvme fabrics target resetting during I/O Daniel Wagner
2025-04-09 17:59 ` Daniel Wagner
2025-04-14 12:10 ` Shinichiro Kawasaki
2025-04-08 16:26 ` [PATCH blktests v2 4/4] nvme/061: add test teardown and setup fabrics target " Daniel Wagner
2025-04-14 12:18 ` Shinichiro Kawasaki
2025-04-14 13:27 ` Daniel Wagner
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=20250408-test-target-v2-1-e9e2512586f8@kernel.org \
--to=wagi@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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.