All of lore.kernel.org
 help / color / mirror / Atom feed
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] f2fs: clean up i_compress_flag and i_compress_level usage
Date: Tue, 31 Jan 2023 19:10:20 +0000	[thread overview]
Message-ID: <167519222014.20142.13564540908735669128.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230128103011.1316979-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Sat, 28 Jan 2023 18:30:11 +0800 you wrote:
> .i_compress_level was introduced by commit 3fde13f817e2 ("f2fs: compress:
> support compress level"), but never be used.
> 
> This patch updates as below:
> - load high 8-bits of on-disk .i_compress_flag to in-memory .i_compress_level
> - load low 8-bits of on-disk .i_compress_flag to in-memory .i_compress_flag
> - change type of in-memory .i_compress_flag from unsigned short to unsigned
> char.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: clean up i_compress_flag and i_compress_level usage
    https://git.kernel.org/jaegeuk/f2fs/c/81649c6e4db8

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

WARNING: multiple messages have this Message-ID (diff)
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] f2fs: clean up i_compress_flag and i_compress_level usage
Date: Tue, 31 Jan 2023 19:10:20 +0000	[thread overview]
Message-ID: <167519222014.20142.13564540908735669128.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230128103011.1316979-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Sat, 28 Jan 2023 18:30:11 +0800 you wrote:
> .i_compress_level was introduced by commit 3fde13f817e2 ("f2fs: compress:
> support compress level"), but never be used.
> 
> This patch updates as below:
> - load high 8-bits of on-disk .i_compress_flag to in-memory .i_compress_level
> - load low 8-bits of on-disk .i_compress_flag to in-memory .i_compress_flag
> - change type of in-memory .i_compress_flag from unsigned short to unsigned
> char.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: clean up i_compress_flag and i_compress_level usage
    https://git.kernel.org/jaegeuk/f2fs/c/81649c6e4db8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2023-01-31 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 10:30 [f2fs-dev] [PATCH] f2fs: clean up i_compress_flag and i_compress_level usage Chao Yu
2023-01-28 10:30 ` Chao Yu
2023-01-31 19:10 ` patchwork-bot+f2fs [this message]
2023-01-31 19:10   ` [f2fs-dev] " patchwork-bot+f2fs

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=167519222014.20142.13564540908735669128.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 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.