From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [intel-lts:pr/69 1/1] fs/f2fs/sysfs.c:448:37: warning: 'f2fs_seq_iostat_info_fops' defined but not used
Date: Mon, 24 Feb 2025 20:52:03 +0800 [thread overview]
Message-ID: <202502242000.Ycal5ow2-lkp@intel.com> (raw)
Hi Chao,
FYI, the error/warning still remains.
tree: https://github.com/intel/linux-intel-lts.git pr/69
head: f36ea6678b4077d9bbb4644e73977fb91d187ab7
commit: b0af6d491a6b5f5622fa91ac75f34f3640f862c4 [1/1] f2fs: add app/fs io stat
config: s390-randconfig-001-20250224 (https://download.01.org/0day-ci/archive/20250224/202502242000.Ycal5ow2-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250224/202502242000.Ycal5ow2-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/202502242000.Ycal5ow2-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/f2fs/sysfs.c:448:37: warning: 'f2fs_seq_iostat_info_fops' defined but not used [-Wunused-const-variable=]
static const struct file_operations f2fs_seq_##_name##_fops = { \
^
fs/f2fs/sysfs.c:457:1: note: in expansion of macro 'F2FS_PROC_FILE_DEF'
F2FS_PROC_FILE_DEF(iostat_info);
^~~~~~~~~~~~~~~~~~
fs/f2fs/sysfs.c:448:37: warning: 'f2fs_seq_segment_bits_fops' defined but not used [-Wunused-const-variable=]
static const struct file_operations f2fs_seq_##_name##_fops = { \
^
fs/f2fs/sysfs.c:456:1: note: in expansion of macro 'F2FS_PROC_FILE_DEF'
F2FS_PROC_FILE_DEF(segment_bits);
^~~~~~~~~~~~~~~~~~
fs/f2fs/sysfs.c:448:37: warning: 'f2fs_seq_segment_info_fops' defined but not used [-Wunused-const-variable=]
static const struct file_operations f2fs_seq_##_name##_fops = { \
^
fs/f2fs/sysfs.c:455:1: note: in expansion of macro 'F2FS_PROC_FILE_DEF'
F2FS_PROC_FILE_DEF(segment_info);
^~~~~~~~~~~~~~~~~~
vim +/f2fs_seq_iostat_info_fops +448 fs/f2fs/sysfs.c
b0af6d491a6b5f5 Chao Yu 2017-08-02 441
8ceffcb29e61ba8 Chao Yu 2017-06-14 442 #define F2FS_PROC_FILE_DEF(_name) \
8ceffcb29e61ba8 Chao Yu 2017-06-14 443 static int _name##_open_fs(struct inode *inode, struct file *file) \
8ceffcb29e61ba8 Chao Yu 2017-06-14 444 { \
8ceffcb29e61ba8 Chao Yu 2017-06-14 445 return single_open(file, _name##_seq_show, PDE_DATA(inode)); \
8ceffcb29e61ba8 Chao Yu 2017-06-14 446 } \
8ceffcb29e61ba8 Chao Yu 2017-06-14 447 \
8ceffcb29e61ba8 Chao Yu 2017-06-14 @448 static const struct file_operations f2fs_seq_##_name##_fops = { \
8ceffcb29e61ba8 Chao Yu 2017-06-14 449 .open = _name##_open_fs, \
8ceffcb29e61ba8 Chao Yu 2017-06-14 450 .read = seq_read, \
8ceffcb29e61ba8 Chao Yu 2017-06-14 451 .llseek = seq_lseek, \
8ceffcb29e61ba8 Chao Yu 2017-06-14 452 .release = single_release, \
8ceffcb29e61ba8 Chao Yu 2017-06-14 453 };
8ceffcb29e61ba8 Chao Yu 2017-06-14 454
:::::: The code at line 448 was first introduced by commit
:::::: 8ceffcb29e61ba882a011b1e4d73ca03691fdc2e f2fs: move sysfs code from super.c to fs/f2fs/sysfs.c
:::::: TO: Chao Yu <yuchao0@huawei.com>
:::::: CC: Jaegeuk Kim <jaegeuk@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-24 12:52 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=202502242000.Ycal5ow2-lkp@intel.com \
--to=lkp@intel.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.