Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] btrfs: fixes and cleanups around messages.c
Date: Thu, 1 Oct 2026 07:24:56 +0930	[thread overview]
Message-ID: <9b41ae47-11ad-4f80-af96-4d26de5caa71@gmx.com> (raw)
In-Reply-To: <cover.1790772326.git.fdmanana@suse.com>



在 2026/9/30 23:55, fdmanana@kernel.org 写道:
> 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.

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> 
> 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(-)
> 


      parent reply	other threads:[~2026-09-30 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 14:25 [PATCH 0/5] btrfs: fixes and cleanups around messages.c fdmanana
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 ` Qu Wenruo [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=9b41ae47-11ad-4f80-af96-4d26de5caa71@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox