[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200202131546.30174-1-chenzhou10@huawei.com>
Date: Sun, 2 Feb 2020 21:15:46 +0800
From: Chen Zhou <chenzhou10@...wei.com>
To: <viro@...iv.linux.org.uk>
CC: <linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<yaohongbo@...wei.com>, <chenzhou10@...wei.com>
Subject: [PATCH -next] fs_parse: make fs_param_bad_value() static
Fix sparse warning:
fs/fs_parser.c:192:5: warning:
symbol 'fs_param_bad_value' was not declared. Should it be static?
Reported-by: Hulk Robot <hulkci@...wei.com>
Signed-off-by: Chen Zhou <chenzhou10@...wei.com>
---
fs/fs_parser.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fs_parser.c b/fs/fs_parser.c
index fdc047b..904e91f 100644
--- a/fs/fs_parser.c
+++ b/fs/fs_parser.c
@@ -189,7 +189,7 @@ int fs_lookup_param(struct fs_context *fc,
}
EXPORT_SYMBOL(fs_lookup_param);
-int fs_param_bad_value(struct p_log *log, struct fs_parameter *param)
+static int fs_param_bad_value(struct p_log *log, struct fs_parameter *param)
{
return inval_plog(log, "Bad value for '%s'", param->key);
}
--
2.7.4
Powered by blists - more mailing lists