From: kbuild test robot <fengguang.wu@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
Evgeniy Dushistov <dushistov@mail.ru>,
linux-kernel@vger.kernel.org
Subject: [PATCH vfs] ufs:: ufs_truncate_blocks() can be static
Date: Thu, 18 Jun 2015 04:04:27 +0800 [thread overview]
Message-ID: <20150617200427.GA998@roam> (raw)
In-Reply-To: <201506180458.e6paay0G%fengguang.wu@intel.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ufs/inode.c b/fs/ufs/inode.c
index 443f85e..0e23a67 100644
--- a/fs/ufs/inode.c
+++ b/fs/ufs/inode.c
@@ -1379,7 +1379,7 @@ out:
return err;
}
-void ufs_truncate_blocks(struct inode *inode)
+static void ufs_truncate_blocks(struct inode *inode)
{
if (!(S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) ||
S_ISLNK(inode->i_mode)))
prev parent reply other threads:[~2015-06-17 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 20:04 [vfs:ufs 143/148] fs/ufs/inode.c:1382:6: sparse: symbol 'ufs_truncate_blocks' was not declared. Should it be static? kbuild test robot
2015-06-17 20:04 ` 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=20150617200427.GA998@roam \
--to=fengguang.wu@intel.com \
--cc=dushistov@mail.ru \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).