Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: sawara04.o@gmail.com, clm@fb.com, josef@toxicpanda.com,
	dsterba@suse.com, johannes.thumshirn@wdc.com, brauner@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Fix and unify mount option log messages
Date: Wed, 13 Aug 2025 10:32:50 +0930	[thread overview]
Message-ID: <8dcfd552-a339-46b4-929e-f01000a4edf1@suse.com> (raw)
In-Reply-To: <20250812180009.1412-1-sawara04.o@gmail.com>



在 2025/8/13 03:30, sawara04.o@gmail.com 写道:
> From: Kyoji Ogasawara <sawara04.o@gmail.com>
> 
> This patch series fixes and unifies the log messages related to btrfs
> mount options.
> 
> The first patch addresses a regression where mount option messages were
> no longer displayed during initial mounts after the fsconfig migration.
> 
> The second patch unifies the log messages for NODATACOW and NODATASUM
> options, which were being handled with the same logic but had
> inconsistent and duplicate messages.

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

Thanks,
Qu
> 
> Thanks,
> Kyoji
> 
> Kyoji Ogasawara (2):
>    btrfs: restore mount option info messages during mount
>    btrfs: Align log messages and fix duplicates for NODATACOW/NODATASUM
> 
>   fs/btrfs/super.c | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
> 


  parent reply	other threads:[~2025-08-13  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 18:00 [PATCH v2 0/2] Fix and unify mount option log messages sawara04.o
2025-08-12 18:00 ` [PATCH v2 1/2] btrfs: restore mount option info messages during mount sawara04.o
2025-08-12 18:00 ` [PATCH v2 2/2] btrfs: Align log messages and fix duplicates for NODATACOW/NODATASUM sawara04.o
2025-08-13  1:02 ` Qu Wenruo [this message]
2025-08-13 10:10 ` [PATCH v2 0/2] Fix and unify mount option log messages David Sterba

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=8dcfd552-a339-46b4-929e-f01000a4edf1@suse.com \
    --to=wqu@suse.com \
    --cc=brauner@kernel.org \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sawara04.o@gmail.com \
    /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