From: kernel test robot <lkp@intel.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [linkinjeon-exfat:dev 1/1] fs/exfat/iomap.c:175:31: warning: unused variable 'exfat_swap_iomap_ops'
Date: Fri, 28 Aug 2026 11:34:15 +0800 [thread overview]
Message-ID: <202608281159.A0nWeJeg-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat.git dev
head: 20cb0bad8c3ad9220aff3e61e8703e17f72bb7f9
commit: 20cb0bad8c3ad9220aff3e61e8703e17f72bb7f9 [1/1] exfat: map allocated extents for swap activation
config: s390-randconfig-001-20260828 (https://download.01.org/0day-ci/archive/20260828/202608281159.A0nWeJeg-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/20260828/202608281159.A0nWeJeg-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/202608281159.A0nWeJeg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/exfat/iomap.c:175:31: warning: unused variable 'exfat_swap_iomap_ops' [-Wunused-const-variable]
175 | static const struct iomap_ops exfat_swap_iomap_ops = {
| ^~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +/exfat_swap_iomap_ops +175 fs/exfat/iomap.c
171
172 static DEFINE_IOMAP_ITER_NEXT(exfat_swap_iomap_next,
173 exfat_swap_iomap_begin);
174
> 175 static const struct iomap_ops exfat_swap_iomap_ops = {
176 .iomap_next = exfat_swap_iomap_next,
177 };
178
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-28 3:34 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=202608281159.A0nWeJeg-lkp@intel.com \
--to=lkp@intel.com \
--cc=linkinjeon@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