From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [chao-linux:dax-wip 7/7] fs/f2fs/file.c:1903:6: warning: no previous prototype for 'dax_mutually_exclusive'
Date: Thu, 01 Apr 2021 02:44:20 +0800 [thread overview]
Message-ID: <202104010214.1qBlByPS-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dax-wip
head: 030db79112b5bc644a842a966bf839ef71a31245
commit: 030db79112b5bc644a842a966bf839ef71a31245 [7/7] f2fs: dax options
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?id=030db79112b5bc644a842a966bf839ef71a31245
git remote add chao-linux https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git
git fetch --no-tags chao-linux dax-wip
git checkout 030db79112b5bc644a842a966bf839ef71a31245
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/f2fs/file.c:1903:6: warning: no previous prototype for 'dax_mutually_exclusive' [-Wmissing-prototypes]
1903 | bool dax_mutually_exclusive(struct inode *inode)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/dax_mutually_exclusive +1903 fs/f2fs/file.c
1902
> 1903 bool dax_mutually_exclusive(struct inode *inode)
1904 {
1905 if (file_is_encrypt(inode))
1906 return false;
1907 if (file_is_verity(inode))
1908 return false;
1909 if (f2fs_has_inline_data(inode))
1910 return true;
1911 return false;
1912 }
1913
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65027 bytes --]
reply other threads:[~2021-03-31 18: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=202104010214.1qBlByPS-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.