All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@kernel.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, Daniel Wagner <wagi@kernel.org>
Subject: [PATCH blktests 1/3] common/nvme: add debug nvmet path variable
Date: Tue, 18 Mar 2025 11:38:59 +0100	[thread overview]
Message-ID: <20250318-test-target-v1-1-01e01142cf2b@kernel.org> (raw)
In-Reply-To: <20250318-test-target-v1-0-01e01142cf2b@kernel.org>

Signed-off-by: Daniel Wagner <wagi@kernel.org>
---
 common/nvme | 1 +
 1 file changed, 1 insertion(+)

diff --git a/common/nvme b/common/nvme
index 3761329d39e3763136f60a4751ad15de347f6e9b..a3176ecff2e5fbc0fbe09460c21e9f50c68d3bce 100644
--- a/common/nvme
+++ b/common/nvme
@@ -26,6 +26,7 @@ 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/"
+NVMET_DFS="/sys/kernel/debug/nvmet/"
 nvme_trtype=${nvme_trtype:-}
 nvme_adrfam=${nvme_adrfam:-}
 

-- 
2.48.1


  reply	other threads:[~2025-03-18 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 10:38 [PATCH blktests 0/3] blktests: add target test cases Daniel Wagner
2025-03-18 10:38 ` Daniel Wagner [this message]
2025-03-18 20:37   ` [PATCH blktests 1/3] common/nvme: add debug nvmet path variable Chaitanya Kulkarni
2025-04-04  8:03   ` Shinichiro Kawasaki
2025-04-04 10:08     ` Daniel Wagner
2025-03-18 10:39 ` [PATCH blktests 2/3] nvme/060: add test nvme fabrics target resetting during I/O Daniel Wagner
2025-03-18 20:40   ` Chaitanya Kulkarni
2025-03-19  9:26     ` Daniel Wagner
2025-03-19 16:54       ` Chaitanya Kulkarni
2025-04-04  8:08   ` Shinichiro Kawasaki
2025-04-04 10:15     ` Daniel Wagner
2025-03-18 10:39 ` [PATCH blktests 3/3] nvme/061: add test teardown and setup fabrics target " Daniel Wagner
2025-03-18 20:42   ` Chaitanya Kulkarni
2025-04-04  8:22   ` Shinichiro Kawasaki
2025-04-04 10:16     ` 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=20250318-test-target-v1-1-01e01142cf2b@kernel.org \
    --to=wagi@kernel.org \
    --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.