mirror of https://lore.kernel.org/lkml/
 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: support to show curseg.next_blkoff in debugfs
Date: Tue, 02 Dec 2025 18:10:06 +0000	[thread overview]
Message-ID: <176469900630.3331097.9220204670598646853.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251128092534.1607427-1-chao@kernel.org>

Hello:

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

On Fri, 28 Nov 2025 17:25:34 +0800 you wrote:
> cat /sys/kernel/debug/f2fs/status
> 
> Main area: 17 segs, 17 secs 17 zones
>     TYPE           blkoff    segno    secno   zoneno  dirty_seg   full_seg  valid_blk
>   - COLD   data:        0        4        4        4          0          0          0
>   - WARM   data:        0        7        7        7          0          0          0
>   - HOT    data:        1        5        5        5          2          0        512
>   - Dir   dnode:        3        0        0        0          1          0          2
>   - File  dnode:        0        1        1        1          0          0          0
>   - Indir nodes:        0        2        2        2          0          0          0
>   - Pinned file:        0       -1       -1       -1
>   - ATGC   data:        0       -1       -1       -1
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: support to show curseg.next_blkoff in debugfs
    https://git.kernel.org/jaegeuk/f2fs/c/20f3430406ae

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



      reply	other threads:[~2025-12-02 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28  9:25 Chao Yu
2025-12-02 18:10 ` 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=176469900630.3331097.9220204670598646853.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
Powered by JetHome