From: kbuild test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: kbuild-all@01.org, linux-unionfs@vger.kernel.org
Subject: [RFC PATCH miklos-vfs] ovl: ovl_fallocate() can be static
Date: Thu, 12 Apr 2018 23:54:09 +0800 [thread overview]
Message-ID: <20180412155409.GA51729@lkp-sb-ep06> (raw)
In-Reply-To: <201804122351.HBN7GKZh%fengguang.wu@intel.com>
Fixes: 9283a5d72622 ("ovl: readd fallocate")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index b7b3202..fd2911b 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -268,7 +268,7 @@ static int ovl_mmap(struct file *file, struct vm_area_struct *vma)
return ret;
}
-long ovl_fallocate(struct file *file, int mode, loff_t offset, loff_t len)
+static long ovl_fallocate(struct file *file, int mode, loff_t offset, loff_t len)
{
struct inode *inode = file_inode(file);
struct fd real;
prev parent 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 [miklos-vfs:overlayfs-rorw 34/54] fs/overlayfs/file.c:271:6: sparse: symbol 'ovl_fallocate' was not declared. Should it be static? kbuild test robot
2018-04-12 15:54 ` 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=20180412155409.GA51729@lkp-sb-ep06 \
--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