public inbox for linux-kernel@vger.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 1/2] f2fs: ro: compress: fix to avoid caching unaligned extent
Date: Mon, 04 Mar 2024 18:20:28 +0000	[thread overview]
Message-ID: <170957642895.16816.4057582792017070117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240226073539.2509926-1-chao@kernel.org>

Hello:

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

On Mon, 26 Feb 2024 15:35:38 +0800 you wrote:
> Mapping info from dump.f2fs:
> i_addr[0x2d] cluster flag    		[0xfffffffe : 4294967294]
> i_addr[0x2e]                 		[0x   10428 : 66600]
> i_addr[0x2f]                 		[0x   10429 : 66601]
> i_addr[0x30]                 		[0x   1042a : 66602]
> 
> f2fs_io fiemap 37 1 /mnt/f2fs/disk-58390c8c.raw
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/2] f2fs: ro: compress: fix to avoid caching unaligned extent
    https://git.kernel.org/jaegeuk/f2fs/c/4b99ecd30429
  - [f2fs-dev,2/2] f2fs: ro: don't start discard thread for readonly image
    https://git.kernel.org/jaegeuk/f2fs/c/a217f1873ab9

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



      parent reply	other threads:[~2024-03-04 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  7:35 [PATCH 1/2] f2fs: ro: compress: fix to avoid caching unaligned extent Chao Yu
2024-02-26  7:35 ` [PATCH 2/2] f2fs: ro: don't start discard thread for readonly image 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=170957642895.16816.4057582792017070117.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