public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: sawara04.o@gmail.com
To: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
	johannes.thumshirn@wdc.com, brauner@kernel.org
Cc: Kyoji Ogasawara <sawara04.o@gmail.com>, linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] Fix and unify mount option log messages
Date: Wed, 13 Aug 2025 03:00:05 +0900	[thread overview]
Message-ID: <20250812180009.1412-1-sawara04.o@gmail.com> (raw)

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.

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

-- 
2.50.1


             reply	other threads:[~2025-08-12 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 18:00 sawara04.o [this message]
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 ` [PATCH v2 0/2] Fix and unify mount option log messages Qu Wenruo
2025-08-13 10:10 ` 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=20250812180009.1412-1-sawara04.o@gmail.com \
    --to=sawara04.o@gmail.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 \
    /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