* [PATCH] bcache: fix kernel-doc warning on CLOSURE_CALLBACK
@ 2026-10-04 23:35 Rosen Penev
0 siblings, 0 replies; only message in thread
From: Rosen Penev @ 2026-10-04 23:35 UTC (permalink / raw)
To: linux-bcache; +Cc: Coly Li, Kent Overstreet, open list
bch_data_insert() is defined through the CLOSURE_CALLBACK() macro, which
kernel-doc cannot see through, so the kernel-doc comment above it
produces:
request.c:308 function parameter 'bch_data_insert' not described in 'CLOSURE_CALLBACK'
request.c:308 expecting prototype for bch_data_insert(). Prototype was for CLOSURE_CALLBACK() instead
Turn it into a regular block comment, and drop the @cl line along
with the kernel-doc markup.
Assisted-by: LLM
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
drivers/md/bcache/request.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/request.c b/drivers/md/bcache/request.c
index 3fa3b13a410f..e7f097346d64 100644
--- a/drivers/md/bcache/request.c
+++ b/drivers/md/bcache/request.c
@@ -285,9 +285,8 @@ static CLOSURE_CALLBACK(bch_data_insert_start)
}
}
-/**
+/*
* bch_data_insert - stick some data in the cache
- * @cl: closure pointer.
*
* This is the starting point for any data to end up in a cache device; it could
* be from a normal write, or a writeback write, or a write to a flash only
--
2.56.0
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-10-04 23:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-04 23:35 [PATCH] bcache: fix kernel-doc warning on CLOSURE_CALLBACK Rosen Penev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®