From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: [bcachefs:bcachefs-testing 129/130] fs/bcachefs/btree_locking.h:428:69: warning: omitting the parameter name in a function definition is a C2x extension
Date: Fri, 12 Apr 2024 14:34:07 +0800 [thread overview]
Message-ID: <202404121412.fTDFGSkH-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head: ecb7f8abc97ccf1ab18363dcd37591329ae42cc2
commit: 60ec285a67d2cdd4ef950a3aed690e8c7f379720 [129/130] bcachefs: Path must be locked if trans->locked && path->should_be_locked
config: i386-randconfig-005-20240412 (https://download.01.org/0day-ci/archive/20240412/202404121412.fTDFGSkH-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240412/202404121412.fTDFGSkH-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/202404121412.fTDFGSkH-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/bcachefs/extents.c:13:
In file included from fs/bcachefs/btree_io.h:7:
>> fs/bcachefs/btree_locking.h:428:69: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
428 | static inline void bch2_btree_path_verify_locks(struct btree_trans *, struct btree_path *path) {}
| ^
1 warning generated.
--
In file included from fs/bcachefs/journal_io.c:5:
In file included from fs/bcachefs/btree_io.h:7:
>> fs/bcachefs/btree_locking.h:428:69: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
428 | static inline void bch2_btree_path_verify_locks(struct btree_trans *, struct btree_path *path) {}
| ^
fs/bcachefs/journal_io.c:1591:35: warning: unused function 'journal_last_unwritten_buf' [-Wunused-function]
1591 | static inline struct journal_buf *journal_last_unwritten_buf(struct journal *j)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
2 warnings generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS
Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n]
Selected by [m]:
- DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM_XE [=m] && DRM_XE [=m]=m
vim +428 fs/bcachefs/btree_locking.h
423
424 #ifdef CONFIG_BCACHEFS_DEBUG
425 void bch2_btree_path_verify_locks(struct btree_trans *, struct btree_path *);
426 void bch2_trans_verify_locks(struct btree_trans *);
427 #else
> 428 static inline void bch2_btree_path_verify_locks(struct btree_trans *, struct btree_path *path) {}
429 static inline void bch2_trans_verify_locks(struct btree_trans *trans) {}
430 #endif
431
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-12 6: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=202404121412.fTDFGSkH-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--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 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.