From: kbuild test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: kbuild-all@01.org, linux-unionfs@vger.kernel.org
Subject: [miklos-vfs:overlayfs-rorw 34/54] fs/overlayfs/file.c:271:6: sparse: symbol 'ovl_fallocate' was not declared. Should it be static?
Date: Thu, 12 Apr 2018 23:54:09 +0800 [thread overview]
Message-ID: <201804122351.HBN7GKZh%fengguang.wu@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-rorw
head: 9b82e69abc05b81650d3be96a50602700fc80bc4
commit: 9283a5d72622b71db31b85d96733d261eafc2dea [34/54] ovl: readd fallocate
reproduce:
# apt-get install sparse
git checkout 9283a5d72622b71db31b85d96733d261eafc2dea
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> fs/overlayfs/file.c:271:6: sparse: symbol 'ovl_fallocate' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2018-04-12 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 15:54 kbuild test robot [this message]
2018-04-12 15:54 ` [RFC PATCH miklos-vfs] ovl: ovl_fallocate() can be static kbuild test robot
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=201804122351.HBN7GKZh%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.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