From: kernel test robot <lkp@intel.com>
To: Alex Markuze <amarkuze@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ceph-devel@vger.kernel.org
Subject: [ceph-client:tls-tracing-only 7/10] lib/blog/blog_core.c:94: warning: Function parameter or struct member 'ctx' not described in 'blog_set_napi_ctx'
Date: Fri, 15 Aug 2025 02:39:01 +0800 [thread overview]
Message-ID: <202508150210.LbtTLrLl-lkp@intel.com> (raw)
tree: https://github.com/ceph/ceph-client.git tls-tracing-only
head: 6b738aa5f6bb2343f8277d318ff1e9ea9289212c
commit: 4dbfb9232bb3bff162418ee08fe5379af0bcab48 [7/10] phase I
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250815/202508150210.LbtTLrLl-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250815/202508150210.LbtTLrLl-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202508150210.LbtTLrLl-lkp@intel.com/
All warnings (new ones prefixed by >>):
lib/blog/blog_core.c:44: warning: Function parameter or struct member 'file' not described in 'blog_get_source_id'
lib/blog/blog_core.c:44: warning: Function parameter or struct member 'func' not described in 'blog_get_source_id'
lib/blog/blog_core.c:44: warning: Function parameter or struct member 'line' not described in 'blog_get_source_id'
lib/blog/blog_core.c:44: warning: Function parameter or struct member 'fmt' not described in 'blog_get_source_id'
lib/blog/blog_core.c:54: warning: Function parameter or struct member 'id' not described in 'blog_get_source_info'
lib/blog/blog_core.c:64: warning: Function parameter or struct member 'source_id' not described in 'blog_log'
lib/blog/blog_core.c:64: warning: Function parameter or struct member 'client_id' not described in 'blog_log'
lib/blog/blog_core.c:64: warning: Function parameter or struct member 'needed_size' not described in 'blog_log'
>> lib/blog/blog_core.c:94: warning: Function parameter or struct member 'ctx' not described in 'blog_set_napi_ctx'
>> lib/blog/blog_core.c:113: warning: Function parameter or struct member 'n' not described in 'blog_log_trim'
>> lib/blog/blog_core.c:123: warning: Function parameter or struct member 'iter' not described in 'blog_log_iter_init'
>> lib/blog/blog_core.c:123: warning: Function parameter or struct member 'pf' not described in 'blog_log_iter_init'
>> lib/blog/blog_core.c:132: warning: Function parameter or struct member 'iter' not described in 'blog_log_iter_next'
>> lib/blog/blog_core.c:143: warning: Function parameter or struct member 'entry' not described in 'blog_des_entry'
>> lib/blog/blog_core.c:143: warning: Function parameter or struct member 'output' not described in 'blog_des_entry'
>> lib/blog/blog_core.c:143: warning: Function parameter or struct member 'out_size' not described in 'blog_des_entry'
>> lib/blog/blog_core.c:143: warning: Function parameter or struct member 'client_cb' not described in 'blog_des_entry'
lib/blog/blog_core.c:153: warning: Function parameter or struct member 'addr' not described in 'blog_is_valid_kernel_addr'
vim +94 lib/blog/blog_core.c
89
90 /**
91 * blog_set_napi_ctx - Set NAPI context for current CPU
92 */
93 void blog_set_napi_ctx(struct blog_tls_ctx *ctx)
> 94 {
95 /* Stub implementation */
96 }
97 EXPORT_SYMBOL(blog_set_napi_ctx);
98
99 /**
100 * blog_get_ctx - Get appropriate context based on context type
101 */
102 struct blog_tls_ctx *blog_get_ctx(void)
103 {
104 /* Stub implementation */
105 return NULL;
106 }
107 EXPORT_SYMBOL(blog_get_ctx);
108
109 /**
110 * blog_log_trim - Trim the current context's pagefrag by n bytes
111 */
112 int blog_log_trim(unsigned int n)
> 113 {
114 /* Stub implementation */
115 return 0;
116 }
117 EXPORT_SYMBOL(blog_log_trim);
118
119 /**
120 * blog_log_iter_init - Initialize the iterator for a specific pagefrag
121 */
122 void blog_log_iter_init(struct blog_log_iter *iter, struct blog_pagefrag *pf)
> 123 {
124 /* Stub implementation */
125 }
126 EXPORT_SYMBOL(blog_log_iter_init);
127
128 /**
129 * blog_log_iter_next - Get next log entry
130 */
131 struct blog_log_entry *blog_log_iter_next(struct blog_log_iter *iter)
> 132 {
133 /* Stub implementation */
134 return NULL;
135 }
136 EXPORT_SYMBOL(blog_log_iter_next);
137
138 /**
139 * blog_des_entry - Deserialize entry with callback
140 */
141 int blog_des_entry(struct blog_log_entry *entry, char *output, size_t out_size,
142 blog_client_des_fn client_cb)
> 143 {
144 /* Stub implementation */
145 return 0;
146 }
147 EXPORT_SYMBOL(blog_des_entry);
148
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-14 18:39 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=202508150210.LbtTLrLl-lkp@intel.com \
--to=lkp@intel.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).