From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix compile warning
Date: Sat, 8 Oct 2022 19:08:52 +0800 [thread overview]
Message-ID: <6d45ea3a-5a71-b760-b60d-9e3e7dda3be4@kernel.org> (raw)
In-Reply-To: <Y0CDoWiaGKHkmnzQ@google.com>
On 2022/10/8 3:53, Jaegeuk Kim wrote:
> Merged into the original patch.
Thanks, so it looks it's not too later to update commit id of original
patch since it's close to the end of merge window.
Thanks,
>
> On 10/06, Chao Yu wrote:
>> fs/f2fs/super.c:3886:6: warning: no previous prototype for 'f2fs_record_stop_reason' [-Wmissing-prototypes]
>>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>> fs/f2fs/super.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>> index fad333881ea2..2908d41ed462 100644
>> --- a/fs/f2fs/super.c
>> +++ b/fs/f2fs/super.c
>> @@ -3884,7 +3884,7 @@ static void save_stop_reason(struct f2fs_sb_info *sbi, unsigned char reason)
>> spin_unlock(&sbi->error_lock);
>> }
>>
>> -void f2fs_record_stop_reason(struct f2fs_sb_info *sbi)
>> +static void f2fs_record_stop_reason(struct f2fs_sb_info *sbi)
>> {
>> struct f2fs_super_block *raw_super = F2FS_RAW_SUPER(sbi);
>> int err;
>> --
>> 2.36.1
next prev parent reply other threads:[~2022-10-08 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 15:14 [PATCH] f2fs: fix compile warning Chao Yu
2022-10-07 19:53 ` Jaegeuk Kim
2022-10-08 11:08 ` Chao Yu [this message]
2022-10-10 17:22 ` Jaegeuk Kim
-- strict thread matches above, loose matches on Subject: below --
2021-03-02 8:44 Chao Yu
2021-03-02 8:49 ` Chao Yu
2020-08-10 10:38 Chao Yu
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=6d45ea3a-5a71-b760-b60d-9e3e7dda3be4@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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