From: David Sterba <dsterba@suse.cz>
To: "小笠原 共志" <sawara04.o@gmail.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
dsterba@suse.cz, clm@fb.com, josef@toxicpanda.com,
dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Implement warning for commit values exceeding 300
Date: Wed, 30 Apr 2025 18:40:46 +0200 [thread overview]
Message-ID: <20250430164046.GK9140@twin.jikos.cz> (raw)
In-Reply-To: <CAKNDObBnpNsyXr4bJeCOQX+d0qrpKMt-LqpE=PMRpyzn=-vtbg@mail.gmail.com>
On Thu, May 01, 2025 at 12:33:32AM +0900, 小笠原 共志 wrote:
> > Sure, that sounds good to me.
>
> Thank you.
>
> I would like to confirm whether the warning message
> "excessive commit interval %u, use with care" is acceptable.
> Please let me know if you have any concerns or suggestions
> for improvement.
Yes, this is OK, thanks.
prev parent reply other threads:[~2025-04-30 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 4:46 [PATCH] btrfs: Implement warning for commit values exceeding 300 sawara04.o
2025-04-28 5:36 ` Qu Wenruo
2025-04-28 15:12 ` David Sterba
[not found] ` <CAKNDObASvhXH3F4jRBHQ2EA6CN+-L-qgg92D2GKAorMu2g9Aig@mail.gmail.com>
2025-04-28 22:19 ` Qu Wenruo
2025-04-30 15:33 ` 小笠原 共志
2025-04-30 16:40 ` David Sterba [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=20250430164046.GK9140@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--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