All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev,
	Kent Overstreet <kent.overstreet@linux.dev>
Subject: [bcachefs:bcachefs-testing 183/184] fs/bcachefs/fs.c:219:1: warning: no return statement in function returning non-void
Date: Mon, 22 Apr 2024 16:18:38 +0800	[thread overview]
Message-ID: <202404221601.RLb8P5Tf-lkp@intel.com> (raw)

tree:   https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head:   b6c8ce298a81e9cfd9d7ed73d3ccb1e737e4fe07
commit: 653cfdde6b4749c4162866b8d9cd858ce3a12525 [183/184] bcachefs: Clean up inode alloc
config: nios2-randconfig-002-20240422 (https://download.01.org/0day-ci/archive/20240422/202404221601.RLb8P5Tf-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240422/202404221601.RLb8P5Tf-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/202404221601.RLb8P5Tf-lkp@intel.com/

All warnings (new ones prefixed by >>):

   fs/bcachefs/fs.c: In function 'bch2_alloc_inode':
>> fs/bcachefs/fs.c:219:1: warning: no return statement in function returning non-void [-Wreturn-type]
     219 | }
         | ^


vim +219 fs/bcachefs/fs.c

   215	
   216	static struct inode *bch2_alloc_inode(struct super_block *sb)
   217	{
   218		BUG();
 > 219	}
   220	

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

                 reply	other threads:[~2024-04-22  8:19 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=202404221601.RLb8P5Tf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kent.overstreet@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.