From: kbuild test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: kbuild-all@lists.01.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, chao@kernel.org,
Chao Yu <yuchao0@huawei.com>,
Park Ju Hyung <qkrwngud825@gmail.com>
Subject: Re: [PATCH] f2fs: use kmem_cache pool during inline xattr lookups
Date: Tue, 25 Feb 2020 16:21:40 +0800 [thread overview]
Message-ID: <202002251648.CP1SCgut%lkp@intel.com> (raw)
In-Reply-To: <20200225014257.83903-1-yuchao0@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 3279 bytes --]
Hi Chao,
I love your patch! Perhaps something to improve:
[auto build test WARNING on f2fs/dev-test]
[cannot apply to v5.6-rc3 next-20200224]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Chao-Yu/f2fs-use-kmem_cache-pool-during-inline-xattr-lookups/20200225-094422
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
config: x86_64-randconfig-s2-20200225 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
# 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 >>):
In file included from fs/f2fs/dir.c:15:0:
fs/f2fs/xattr.h: In function 'f2fs_destroy_xattr_caches':
>> fs/f2fs/xattr.h:157:74: warning: 'return' with a value, in function returning void
static void f2fs_destroy_xattr_caches(struct f2fs_sb_info *sbi) { return 0; }
^
fs/f2fs/xattr.h:157:13: note: declared here
static void f2fs_destroy_xattr_caches(struct f2fs_sb_info *sbi) { return 0; }
^~~~~~~~~~~~~~~~~~~~~~~~~
At top level:
fs/f2fs/xattr.h:157:13: warning: 'f2fs_destroy_xattr_caches' defined but not used [-Wunused-function]
fs/f2fs/xattr.h:156:12: warning: 'f2fs_init_xattr_caches' defined but not used [-Wunused-function]
static int f2fs_init_xattr_caches(struct f2fs_sb_info *sbi) { return 0; }
^~~~~~~~~~~~~~~~~~~~~~
--
In file included from fs/f2fs/super.c:31:0:
fs/f2fs/xattr.h: In function 'f2fs_destroy_xattr_caches':
>> fs/f2fs/xattr.h:157:74: warning: 'return' with a value, in function returning void
static void f2fs_destroy_xattr_caches(struct f2fs_sb_info *sbi) { return 0; }
^
fs/f2fs/xattr.h:157:13: note: declared here
static void f2fs_destroy_xattr_caches(struct f2fs_sb_info *sbi) { return 0; }
^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/return +157 fs/f2fs/xattr.h
137
138 #define f2fs_xattr_handlers NULL
139 static inline int f2fs_setxattr(struct inode *inode, int index,
140 const char *name, const void *value, size_t size,
141 struct page *page, int flags)
142 {
143 return -EOPNOTSUPP;
144 }
145 static inline int f2fs_getxattr(struct inode *inode, int index,
146 const char *name, void *buffer,
147 size_t buffer_size, struct page *dpage)
148 {
149 return -EOPNOTSUPP;
150 }
151 static inline ssize_t f2fs_listxattr(struct dentry *dentry, char *buffer,
152 size_t buffer_size)
153 {
154 return -EOPNOTSUPP;
155 }
156 static int f2fs_init_xattr_caches(struct f2fs_sb_info *sbi) { return 0; }
> 157 static void f2fs_destroy_xattr_caches(struct f2fs_sb_info *sbi) { return 0; }
158 #endif
159
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38836 bytes --]
prev parent reply other threads:[~2020-02-25 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 1:42 Chao Yu
2020-02-25 6:37 ` Ju Hyung Park
2020-02-25 8:44 ` Chao Yu
2020-02-25 8:21 ` kbuild test robot [this message]
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=202002251648.CP1SCgut%lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qkrwngud825@gmail.com \
--cc=yuchao0@huawei.com \
/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
Powered by JetHome