From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: introduce SEGS_TO_BLKS/BLKS_TO_SEGS for cleanup
Date: Mon, 04 Mar 2024 18:20:28 +0000 [thread overview]
Message-ID: <170957642882.16816.9297901358493884285.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240304032855.1425579-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 4 Mar 2024 11:28:55 +0800 you wrote:
> Just cleanup, no functional change.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> v2:
> - don't cast type of segment number from unsigned int
> to long long, because segs << log_blocks_per_seg won't
> overflow due to f2fs doesn't support 64-bits addressing.
> fs/f2fs/debug.c | 7 +++----
> fs/f2fs/f2fs.h | 14 ++++++++------
> fs/f2fs/gc.c | 10 +++++-----
> fs/f2fs/gc.h | 4 ++--
> fs/f2fs/segment.c | 12 ++++++------
> fs/f2fs/segment.h | 15 +++++++--------
> fs/f2fs/super.c | 16 ++++++++--------
> fs/f2fs/sysfs.c | 4 ++--
> 8 files changed, 41 insertions(+), 41 deletions(-)
Here is the summary with links:
- [f2fs-dev,v2] f2fs: introduce SEGS_TO_BLKS/BLKS_TO_SEGS for cleanup
https://git.kernel.org/jaegeuk/f2fs/c/45809cd3bdac
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
prev parent reply other threads:[~2024-03-04 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 3:28 [f2fs-dev] [PATCH v2] f2fs: introduce SEGS_TO_BLKS/BLKS_TO_SEGS for cleanup Chao Yu
2024-03-04 18:20 ` patchwork-bot+f2fs [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=170957642882.16816.9297901358493884285.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).