From: patchwork-bot+f2fs@kernel.org
To: Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: jaegeuk@kernel.org, lvc-patches@linuxtesting.org,
lvc-project@linuxtesting.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH REPOST] f2fs: file: drop useless initializer in expand_inode_data()
Date: Mon, 09 Jan 2023 22:51:14 +0000 [thread overview]
Message-ID: <167330467437.13717.6089635302778662185.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <38010b42-afd3-5394-09df-2378b7b5d10f@omp.ru>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 20 Dec 2022 20:17:32 +0300 you wrote:
> In expand_inode_data(), the 'new_size' local variable is initialized to
> the result of i_size_read(), however this value isn't ever used, so we
> can drop this initializer...
>
> Found by Linux Verification Center (linuxtesting.org) with the SVACE static
> analysis tool.
>
> [...]
Here is the summary with links:
- [f2fs-dev,REPOST] f2fs: file: drop useless initializer in expand_inode_data()
https://git.kernel.org/jaegeuk/f2fs/c/39bee2e6acc2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-01-09 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 17:17 [f2fs-dev] [PATCH REPOST] f2fs: file: drop useless initializer in expand_inode_data() Sergey Shtylyov
2022-12-21 12:22 ` Chao Yu
2023-01-09 22:51 ` patchwork-bot+f2fs [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 3:30 Yangtao Li via Linux-f2fs-devel
2022-12-21 12:34 ` Chao Yu
2022-12-21 14:55 ` Sergey Shtylyov
2022-12-21 14:46 ` Sergey Shtylyov
2022-12-21 14:50 ` Sergey Shtylyov
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=167330467437.13717.6089635302778662185.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=lvc-patches@linuxtesting.org \
--cc=lvc-project@linuxtesting.org \
--cc=s.shtylyov@omp.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.