From: Zhangshaokun <zhangshaokun@hisilicon.com>
To: Chao Yu <yuchao0@huawei.com>, linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [RESEND PATCH] f2fs: Fix one GCC warning
Date: Tue, 23 Apr 2019 11:31:01 +0800 [thread overview]
Message-ID: <264958c8-779e-db74-dbae-4e97d136f59f@hisilicon.com> (raw)
In-Reply-To: <eab291f6-7271-2094-9362-e5174685d856@huawei.com>
Hi,
On 2019/4/23 10:57, Chao Yu wrote:
> On 2019/4/22 21:27, Shaokun Zhang wrote:
>> fs/f2fs/node.c: In function ‘f2fs_remove_inode_page’:
>> fs/f2fs/node.c:1193:47: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 5 has type ‘blkcnt_t {aka long long unsigned int}’ [-Wformat=]
>> "Inconsistent i_blocks, ino:%lu, iblocks:%lu",
>> ~~^
>> %llu
>> inode->i_ino, inode->i_blocks);
>> ~~~~~~~~~~~~~~~
>> Fixes: cdad635bd068 ("f2fs: fix to avoid panic in f2fs_remove_inode_page()")
>
> We have already fixed this issue, thanks for noticing this issue. :)
>
Nice, thanks your reply.
> https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test&id=5cf2879fa71a865f08348dae982b97b9738a0847
>
> Thanks,
>
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2019-04-23 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 13:27 [RESEND PATCH] f2fs: Fix one GCC warning Shaokun Zhang
2019-04-23 2:57 ` Chao Yu
2019-04-23 3:31 ` Zhangshaokun [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=264958c8-779e-db74-dbae-4e97d136f59f@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
/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).