[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200701152858.50516-1-weiyongjun1@huawei.com>
Date: Wed, 1 Jul 2020 23:28:58 +0800
From: Wei Yongjun <weiyongjun1@...wei.com>
To: <hulkcommits@...wei.com>, Jaegeuk Kim <jaegeuk@...nel.org>,
Chao Yu <chao@...nel.org>
CC: Hulk Robot <hulkci@...wei.com>,
<linux-f2fs-devel@...ts.sourceforge.net>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH -next] f2fs: make __allocate_new_segment() static
From: Hulk Robot <hulkci@...wei.com>
From: Hulk Robot <hulkci@...wei.com>
Fix sparse build warning:
fs/f2fs/segment.c:2736:6: warning:
symbol '__allocate_new_segment' was not declared. Should it be static?
Signed-off-by: Hulk Robot <hulkci@...wei.com>
---
fs/f2fs/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index b45e473508a9..c35614d255e1 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -2733,7 +2733,7 @@ void f2fs_allocate_segment_for_resize(struct f2fs_sb_info *sbi, int type,
up_read(&SM_I(sbi)->curseg_lock);
}
-void __allocate_new_segment(struct f2fs_sb_info *sbi, int type)
+static void __allocate_new_segment(struct f2fs_sb_info *sbi, int type)
{
struct curseg_info *curseg = CURSEG_I(sbi, type);
unsigned int old_segno;
Powered by blists - more mailing lists