From: Ethan Nelson-Moore <enelsonmoore@gmail.com>
To: cgroups@vger.kernel.org, linux-block@vger.kernel.org
Cc: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
Tejun Heo <tj@kernel.org>, Josef Bacik <josef@toxicpanda.com>,
Jens Axboe <axboe@kernel.dk>
Subject: [PATCH] blk-iocost: correct CONFIG_TRACEPOINTS macro name in comments
Date: Sat, 13 Jun 2026 15:54:26 -0700 [thread overview]
Message-ID: <20260613225427.139129-1-enelsonmoore@gmail.com> (raw)
Comments in block/blk-iocost.c incorrectly refer to
CONFIG_TRACE_POINTS instead of CONFIG_TRACEPOINTS. Correct them.
Discovered while searching for CONFIG_* symbols referenced in code but
not defined in any Kconfig file.
Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
---
block/blk-iocost.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/blk-iocost.c b/block/blk-iocost.c
index 0cca88a366dc..04630c36b737 100644
--- a/block/blk-iocost.c
+++ b/block/blk-iocost.c
@@ -205,9 +205,9 @@ static char trace_iocg_path[TRACE_IOCG_PATH_LEN];
} \
} while (0)
-#else /* CONFIG_TRACE_POINTS */
+#else /* CONFIG_TRACEPOINTS */
#define TRACE_IOCG_PATH(type, iocg, ...) do { } while (0)
-#endif /* CONFIG_TRACE_POINTS */
+#endif /* CONFIG_TRACEPOINTS */
enum {
MILLION = 1000000,
--
2.43.0
reply other threads:[~2026-06-13 22:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260613225427.139129-1-enelsonmoore@gmail.com \
--to=enelsonmoore@gmail.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=tj@kernel.org \
/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