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: sysfs: add encoding_flags entry
Date: Mon, 28 Apr 2025 22:40:52 +0000 [thread overview]
Message-ID: <174588005248.1067750.11308178018864136202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250416054805.1416834-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 16 Apr 2025 13:48:04 +0800 you wrote:
> This patch adds a new sysfs entry /sys/fs/f2fs/<disk>/encoding_flags,
> it is a read-only entry to show the value of sb.s_encoding_flags, the
> value is hexadecimal.
>
> =========================== ==========
> Flag_Name Flag_Value
> =========================== ==========
> SB_ENC_STRICT_MODE_FL 0x00000001
> SB_ENC_NO_COMPAT_FALLBACK_FL 0x00000002
> =========================== ==========
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: sysfs: add encoding_flags entry
https://git.kernel.org/jaegeuk/f2fs/c/0d56663919d2
- [f2fs-dev,2/2] f2fs: sysfs: export linear_lookup in features directory
https://git.kernel.org/jaegeuk/f2fs/c/217fc63224a9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-04-28 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 5:48 Chao Yu
2025-04-16 5:48 ` [PATCH 2/2] f2fs: sysfs: export linear_lookup in features directory Chao Yu
2025-04-28 22:40 ` patchwork-bot+f2fs [this message]
2025-06-24 10:00 ` [STABLE 5.15+] f2fs: sysfs: add encoding_flags entry Lee Jones
2025-07-02 10:20 ` Greg Kroah-Hartman
2025-07-23 8:26 ` Lee Jones
2025-07-23 9:41 ` Greg Kroah-Hartman
2025-07-24 10:18 ` Lee Jones
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=174588005248.1067750.11308178018864136202.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
all inboxes | Powered by JetHome®