linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kmo@daterainc.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 3379/3551] fs/bcachefs/buckets.c:316:21: warning: no previous prototype for 'bucket_m_to_alloc'
Date: Mon, 27 Nov 2023 17:43:50 +0800	[thread overview]
Message-ID: <202311271541.YjOfLYSX-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   48bbaf8b793e0770798519f8ee1ea2908ff0943a
commit: 8192d6956cb6798c4cb28d35712373c9af7897bf [3379/3551] bcachefs: New bucket sector count helpers
config: i386-buildonly-randconfig-001-20231127 (https://download.01.org/0day-ci/archive/20231127/202311271541.YjOfLYSX-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231127/202311271541.YjOfLYSX-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/202311271541.YjOfLYSX-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from fs/bcachefs/buckets.c:17:
   fs/bcachefs/error.h: In function 'bch2_bkey_fsck_err':
   fs/bcachefs/error.h:168:9: warning: function 'bch2_bkey_fsck_err' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
     168 |         prt_vprintf(err_msg, fmt, args);
         |         ^~~~~~~~~~~
   fs/bcachefs/buckets.c: At top level:
>> fs/bcachefs/buckets.c:316:21: warning: no previous prototype for 'bucket_m_to_alloc' [-Wmissing-prototypes]
     316 | struct bch_alloc_v4 bucket_m_to_alloc(struct bucket b)
         |                     ^~~~~~~~~~~~~~~~~


vim +/bucket_m_to_alloc +316 fs/bcachefs/buckets.c

   315	
 > 316	struct bch_alloc_v4 bucket_m_to_alloc(struct bucket b)
   317	{
   318		return (struct bch_alloc_v4) {
   319			.gen		= b.gen,
   320			.data_type	= b.data_type,
   321			.dirty_sectors	= b.dirty_sectors,
   322			.cached_sectors	= b.cached_sectors,
   323			.stripe		= b.stripe,
   324		};
   325	}
   326	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2023-11-27  9:44 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=202311271541.YjOfLYSX-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kmo@daterainc.com \
    --cc=linux-mm@kvack.org \
    --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