From 3bb34b1b1f4c54791bbec32cdda9b8b7e2f76dd0 Mon Sep 17 00:00:00 2001
From: Oleksandr Pavlyk <21087696+oleksandr-pavlyk@users.noreply.github.com>
Date: Mon, 28 Jul 2025 07:54:16 -0500
Subject: [PATCH] Remove suggestion to use --disable-blocking-kernel

The text printed when blocking kernel times out already suggests to
use --profile option.
---
 nvbench/blocking_kernel.cu | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/nvbench/blocking_kernel.cu b/nvbench/blocking_kernel.cu
index 9514ee6..d9cb975 100644
--- a/nvbench/blocking_kernel.cu
+++ b/nvbench/blocking_kernel.cu
@@ -83,7 +83,7 @@ __global__ void block_stream(const volatile nvbench::int32_t *flag,
            "NVBench documentation.\n"
            "\n"
            "If this happens while profiling with an external tool,\n"
-           "pass the `--disable-blocking-kernel` flag or the `--profile` flag\n"
+           "the `--profile` flag\n"
            "(to also only run the benchmark once) to the executable.\n"
            "\n"
            "For more information, see the 'Benchmark Properties' section of the\n"