From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] btrfs: fixes and cleanups around messages.c
Date: Wed, 30 Sep 2026 15:25:33 +0100 [thread overview]
Message-ID: <cover.1790772326.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Fix a couple bugs when building the fs state string for printing in
messages and a few related cleanups in this area.
Filipe Manana (5):
btrfs: fix incomplete iteration over fs state when logging messages
btrfs: fix duplicated code in fs state string in logged messages
btrfs: add missing code for no delayed iput fs state in log messages
btrfs: remove unncessary pointer increment in btrfs_state_to_string()
btrfs: avoid overhead when logging messages if fs state is clean
fs/btrfs/messages.c | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)
--
2.47.2
next reply other threads:[~2026-09-30 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:25 fdmanana [this message]
2026-09-30 14:25 ` [PATCH 1/5] btrfs: fix incomplete iteration over fs state when logging messages fdmanana
2026-09-30 14:25 ` [PATCH 2/5] btrfs: fix duplicated code in fs state string in logged messages fdmanana
2026-09-30 14:25 ` [PATCH 3/5] btrfs: add missing code for no delayed iput fs state in log messages fdmanana
2026-09-30 14:25 ` [PATCH 4/5] btrfs: remove unncessary pointer increment in btrfs_state_to_string() fdmanana
2026-09-30 14:25 ` [PATCH 5/5] btrfs: avoid overhead when logging messages if fs state is clean fdmanana
2026-09-30 21:54 ` [PATCH 0/5] btrfs: fixes and cleanups around messages.c Qu Wenruo
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=cover.1790772326.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=linux-btrfs@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.