From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] f2fs: Fix signedness bugs in f2fs_gc_pinned_control functions
Date: Fri, 15 Apr 2022 13:28:17 -0700 [thread overview]
Message-ID: <YlnVYb34gNtFcQzt@google.com> (raw)
In-Reply-To: <dc6e857f-68bd-2028-35cb-ebb34d5facba@kernel.org>
On 04/15, Chao Yu wrote:
> On 2022/4/15 16:49, Jiapeng Chong wrote:
> > Fix the following smatch warning:
> >
> > fs/f2fs/gc.c:688 f2fs_gc_pinned_control() warn: signedness bug returning
> > '(-16)'.
>
> Oops, thanks for catching this...
>
> It's better to merge this patch into original patch, if you don't mind?
Applied.
>
> Thanks,
prev parent reply other threads:[~2022-04-15 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 8:49 [PATCH] f2fs: Fix signedness bugs in f2fs_gc_pinned_control functions Jiapeng Chong
2022-04-15 9:33 ` Chao Yu
2022-04-15 20:28 ` Jaegeuk Kim [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=YlnVYb34gNtFcQzt@google.com \
--to=jaegeuk@kernel.org \
--cc=abaci@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=jiapeng.chong@linux.alibaba.com \
--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