From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:ceph-iter 49/92] fs/afs/write.c:313:13: warning: 'netfs_dump_sg' defined but not used
Date: Sat, 30 Nov 2024 04:14:02 +0800 [thread overview]
Message-ID: <202411300454.2MPbBgrd-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git ceph-iter
head: ae69436bf8db8f3a53edd0dfa379e753700240c0
commit: 60df3102afd636c54591818d78bc1b3965a9a6f3 [49/92] afs: [DON'T MERGE] Implement trivial content crypto for testing purposes
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20241130/202411300454.2MPbBgrd-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241130/202411300454.2MPbBgrd-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/202411300454.2MPbBgrd-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/afs/write.c:313:13: warning: 'netfs_dump_sg' defined but not used [-Wunused-function]
313 | static void netfs_dump_sg(const char *prefix, struct scatterlist *sg, unsigned int n_sg)
| ^~~~~~~~~~~~~
vim +/netfs_dump_sg +313 fs/afs/write.c
312
> 313 static void netfs_dump_sg(const char *prefix, struct scatterlist *sg, unsigned int n_sg)
314 {
315 unsigned int i;
316
317 for (i = 0; i < n_sg; i++) {
318 void *p = kmap_local_page(sg_page(sg));
319 unsigned int l = min_t(size_t, sg->length, 16);
320
321 printk("%s[%x] %016lx %04x %04x %*phN\n",
322 prefix, i, sg->page_link, sg->offset, sg->length,
323 l, p + sg->offset);
324 kunmap_local(p);
325 sg++;
326 }
327 }
328
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-29 20:14 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=202411300454.2MPbBgrd-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--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 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.