From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC] fuse: add generic file store
Date: Wed, 02 Jun 2021 10:39:33 +0800 [thread overview]
Message-ID: <202106021005.8T07QmHT-lkp@intel.com> (raw)
In-Reply-To: <1622537906-54361-1-git-send-email-tao.peng@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
Hi Peng,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on v5.13-rc4]
[also build test WARNING on next-20210601]
[cannot apply to fuse/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Peng-Tao/fuse-add-generic-file-store/20210601-170405
base: 8124c8a6b35386f73523d27eacb71b5364a68c4c
config: x86_64-randconfig-s022-20210601 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/7f4d572f64348205578780f5a994676ae3a8bd78
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Peng-Tao/fuse-add-generic-file-store/20210601-170405
git checkout 7f4d572f64348205578780f5a994676ae3a8bd78
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/fuse/inode.c:36:1: sparse: sparse: symbol 'fuse_filp_store' was not declared. Should it be static?
>> fs/fuse/inode.c:37:1: sparse: sparse: symbol 'fuse_filp_store_mutex' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 37815 bytes --]
next prev parent reply other threads:[~2021-06-02 2:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:58 [PATCH RFC] fuse: add generic file store Peng Tao
2021-06-02 2:39 ` kernel test robot [this message]
2021-06-02 2:39 ` [RFC PATCH] fuse: fuse_filp_store can be static kernel test robot
2021-06-02 15:50 ` [PATCH RFC] fuse: add generic file store Alessio Balsini
2021-06-07 7:46 ` Peng Tao
2021-06-07 15:32 ` Enrico Weigelt, metux IT consult
2021-06-08 2:58 ` Peng Tao
2021-06-08 10:49 ` Enrico Weigelt, metux IT consult
2021-06-08 12:41 ` Peng Tao
2021-06-09 12:54 ` Enrico Weigelt, metux IT consult
2021-06-11 12:46 ` Peng Tao
2021-06-15 18:50 ` Enrico Weigelt, metux IT consult
2021-06-16 10:20 ` Peng Tao
2021-06-16 16:09 ` Enrico Weigelt, metux IT consult
2021-06-17 13:23 ` Peng Tao
2021-06-21 19:05 ` Enrico Weigelt, metux IT consult
2021-06-22 6:46 ` Peng Tao
2021-06-24 14:19 ` Enrico Weigelt, metux IT consult
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=202106021005.8T07QmHT-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.