From: kbuild test robot <fengguang.wu@intel.com>
To: Michael Halcrow <mhalcrow@google.com>
Cc: kbuild-all@01.org, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH ext4] ext4 crypto: ext4_xattr_encryption_context_set() can be static
Date: Fri, 16 Jan 2015 10:07:13 +0800 [thread overview]
Message-ID: <20150116020713.GA50649@snb> (raw)
In-Reply-To: <201501161001.0s7ByimN%fengguang.wu@intel.com>
fs/ext4/xattr_encryption.c:80:5: sparse: symbol 'ext4_xattr_encryption_context_set' was not declared. Should it be static?
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
xattr_encryption.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/xattr_encryption.c b/fs/ext4/xattr_encryption.c
index d03697a..851064a 100644
--- a/fs/ext4/xattr_encryption.c
+++ b/fs/ext4/xattr_encryption.c
@@ -77,7 +77,7 @@ static int ext4_xattr_encryption_set(struct dentry *dentry, const char *name,
* Made as a separate function on purpose, so that setting this value from user
* space tools is not available through generic set attribute path.
*/
-int ext4_xattr_encryption_context_set(struct dentry *dentry, const void *value,
+static int ext4_xattr_encryption_context_set(struct dentry *dentry, const void *value,
size_t size, int flags, int type)
{
return ext4_xattr_set(dentry->d_inode,
prev parent reply other threads:[~2015-01-16 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 2:07 [ext4:crypto 8/21] fs/ext4/xattr_encryption.c:80:5: sparse: symbol 'ext4_xattr_encryption_context_set' was not declared. Should it be static? kbuild test robot
2015-01-16 2:07 ` 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=20150116020713.GA50649@snb \
--to=fengguang.wu@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=kbuild-all@01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=tytso@mit.edu \
/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).