From: kbuild test robot <lkp@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: fs/ceph/debugfs.c:297:2: warning: 'return' with a value, in function returning void
Date: Thu, 25 Jul 2019 13:32:25 +0800 [thread overview]
Message-ID: <201907251320.jFVuSEz5%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
head: bed38c3e2dca01b358a62b5e73b46e875742fd75
commit: 1a829ff2a6c37187ff8020488e84ec392cb94854 ceph: no need to check return value of debugfs_create functions
date: 3 weeks ago
config: x86_64-randconfig-s1-07251243 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout 1a829ff2a6c37187ff8020488e84ec392cb94854
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
fs/ceph/debugfs.c: In function 'ceph_fs_debugfs_init':
>> fs/ceph/debugfs.c:297:2: warning: 'return' with a value, in function returning void
return 0;
^
vim +/return +297 fs/ceph/debugfs.c
039934b8 Sage Weil 2009-11-12 294
1a829ff2 Greg Kroah-Hartman 2019-06-12 295 void ceph_fs_debugfs_init(struct ceph_fs_client *fsc)
039934b8 Sage Weil 2009-11-12 296 {
039934b8 Sage Weil 2009-11-12 @297 return 0;
039934b8 Sage Weil 2009-11-12 298 }
039934b8 Sage Weil 2009-11-12 299
:::::: The code at line 297 was first introduced by commit
:::::: 039934b895c89c2bb40aa5132efe00e60b70efca ceph: build cleanly without CONFIG_DEBUG_FS
:::::: TO: Sage Weil <sage@newdream.net>
:::::: CC: Sage Weil <sage@newdream.net>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29177 bytes --]
reply other threads:[~2019-07-25 5:32 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=201907251320.jFVuSEz5%lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®